Intent MCP Server

Created By
aintenta year ago
A Model Context Protocol server for processing travel intents based on Deep Intent Architecture. This server provides a robust API for managing travel intents, generating deep flows, and creating DIML (Deep Intent Markup Language) representations.
Overview

What is Intent MCP Server?

Intent MCP Server is a Model Context Protocol server designed to process natural language travel intents into structured, actionable formats using Deep Intent Architecture.

How to use Intent MCP Server?

To use the Intent MCP Server, clone the repository, install dependencies, configure environment variables, and start the server for development or production.

Key features of Intent MCP Server?

  • 🎯 Intent Processing: Create, retrieve, and process intents through a well-defined API.
  • 🔍 Natural Language Understanding: Parse and understand raw user intentions.
  • 🧩 Intent Decomposition: Transform intentions into structured objects with goals and constraints.
  • 💾 Flexible Storage: Pluggable storage system with built-in in-memory implementation.
  • 📝 Type Safety: Full TypeScript implementation with comprehensive type definitions.
  • 🛡️ Error Handling: Robust error handling and logging system.
  • 🧪 Testing: Comprehensive test suite with Jest.
  • 📚 API Documentation: Clear API documentation and examples.

Use cases of Intent MCP Server?

  1. Managing travel-related intents for applications.
  2. Automating workflows based on user travel requests.
  3. Enhancing natural language processing capabilities in travel applications.

FAQ from Intent MCP Server?

  • Can Intent MCP Server handle multiple languages?

Yes! The server can be extended to support multiple languages for intent processing.

  • Is there a limit to the number of intents?

No, the server is designed to handle a large number of intents efficiently.

  • How can I contribute to the project?

You can contribute by forking the repository, creating a feature branch, and submitting a pull request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
aintent
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

3 hours ago
Myrsu
@VidhiJav

2 days ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago