Beckn Mobility

You are building and running a Beckn Mobility MCP Server that acts as a Buyer Application Platform (BAP). It lets AI agents search for cabs, view prices, and book rides within Beckn-enabled mobility ecosystems. This server handles asynchronous Beckn callbacks, signs requests securely with Ed25519, and exposes MCP tools for AI-driven interaction through a high-performance Hono-based HTTP surface and SSE streaming.

How to use

You will connect an MCP client to this server to perform mobility tasks. The server exposes tools for searching cabs, selecting a ride, initiating a booking, and confirming a booking. Use an MCP client that can consume these tools via the SSE endpoint exposed by the server. You can run the server locally, expose it publicly, and connect your AI agent to the SSE stream to receive real-time updates as you search and book rides.

How to install

Prerequisites: ensure you have Node.js v18 or later installed on your machine.

Clone the project directory and install dependencies.

Run the local development server and expose it for webhooks.

Install steps

# Clone the repository
git clone https://github.com/<YOUR_USERNAME>/mcp-beckn-mobility.git
cd mcp-beckn-mobility

# Install dependencies
npm install

# Start the server in development mode
npm run dev

# If you need to expose the local server publicly for webhooks
# (generate a public URL for testing)
ngrok http 3000

Configure and run locally with public URL

Set up environment variables to configure your MCP client and registry integration.

Copy the example env file, fill in your details, and start the server.

Order of operations for local development

1. Generate Ed25519 signing keys for request signing. 2) Create a public BAP URI and register with the Beckn Registry. 3) Start the server and expose it publicly if needed for callbacks.

Use with an MCP client

Configure your MCP client to connect to the SSE endpoint at the server. If you run locally with a public URL, update the BAP_URI in your environment to that URL.

Security and verification

The server implements Ed25519 request signing for Beckn Registry compatibility and includes verification scripts to validate crypto signing and end-to-end flows.

Verification

Run the provided verification scripts to check cryptography and full flow, ensuring your setup is sound before going live.

Project structure

Key source areas include the main server entry, MCP tool definitions, Beckn protocol client, webhook management, and the Hono transport layer.

License

MIT license.

Available tools

search_cabs

Tool to search for available cabs within the Beckn Mobility ecosystem using AI agents.

select_ride

Tool to select a preferred ride option from search results.

init_booking

Tool to initiate the booking process after a ride is selected.

confirm_booking

Tool to confirm and finalize the booking with the BPP.