majjha.developers
Open beta

Public beta: activity uses test Dots with no monetary value. There is no money in or out, and interfaces may change before launch.

MCP server

Preview the remote OAuth gateway that will let AI clients read majjha markets and submit beta trades from a chat.

Not deployed yet

The OAuth-complete gateway remains a preview and the hosted endpoint is not live. The hostname and client setup below are reserved connection details, not a working service.

Beta account scope

Once deployed, the gateway will act on the signed-in majjha account. During the beta that means the same test Dots shown in the app. They have no monetary value, with no money in or out.

How it works

The planned remote MCP serveruses streamable HTTP. It will not require a manually managed API key: the first connection will open majjha's OAuth flow, ask for consent, and let the client keep the resulting account-scoped session.

  • OAuth removes the need to copy, paste, or rotate a gateway API key.
  • The protocol is designed for MCP clients that support streamable HTTP.
  • Consent will offer read only or read + trade.

Connection flow (once live)

1. Have a majjha account

Any beta account will use the same valueless test balance as the app.

2. Add the server

Add https://mcp.majjha.fun/mcp in your AI client's MCP settings.

3. Approve the sign-in

Sign in to majjha in your browser to grant the client access.

4. Use beta tools

Ask your assistant to find markets, check books, or place a test trade.

Server endpoint

The reserved streamable HTTP endpoint is:

Streamable HTTP
https://mcp.majjha.fun/mcp

The deployed gateway will use streamable HTTP, so compatible clients will connect directly without a local helper service.

Authentication

The gateway is designed for OAuth 2.1 with your majjha account. On first connection, a client will open a browser window for sign-in and consent, then keep the resulting session. Clients will discover the OAuth configuration through standard well-known URLs:

ResourceURL
Protected resource metadatahttps://mcp.majjha.fun/.well-known/oauth-protected-resource
Authorization server metadatahttps://mcp.majjha.fun/.well-known/oauth-authorization-server

Two scopes are offered at sign-in: read (markets & your portfolio) and trade(place & cancel orders). Grant only what you need.

Reserved client configuration

Once the service launches, clients will use the same details: name predictmax, URL https://mcp.majjha.fun/mcp, authentication OAuth.

Claude Code

one command
claude mcp add --transport http predictmax https://mcp.majjha.fun/mcp

Once the gateway is deployed, the first call will open the OAuth flow in your browser.

Cursor

Settings → MCP → Add new global MCP server, then paste:

~/.cursor/mcp.json
{
  "mcpServers": {
    "predictmax": {
      "url": "https://mcp.majjha.fun/mcp"
    }
  }
}

Claude Web & ChatGPT

  • Claude Web: Profile → Customize → Connectors → Add custom connector → name predictmax, URL https://mcp.majjha.fun/mcp, finish the OAuth sign-in.
  • ChatGPT: Settings → Advanced → Developer mode → Apps → Create → name predictmax, URL https://mcp.majjha.fun/mcp, choose OAuth.

Other clients (Windsurf, VS Code, Codex…) follow the same idea: add https://mcp.majjha.fun/mcp as a streamable HTTP server and finish the OAuth sign-in.

Tools

These are the planned catalogue groups. After deployment, tools/list will be the source of truth.

Market data

— Public reads — available to any connected client.
  • get_exchange_statusCheck the exchange is operational.
  • list_marketsList/search markets by status, category or text.
  • get_marketFetch a single market by ticker.
  • get_orderbookCurrent bids/asks, spread and mid for a market.
  • get_market_tradesRecent public trades for a market.
  • list_seriesList recurring market families (series).
  • list_eventsList events, optionally within a series.

Trading & portfolio

— Act on your account — require the trade scope you grant at sign-in.
  • get_balancetrade / portfolioCash balance and total portfolio value.
  • list_positionstrade / portfolioOpen positions with value and P&L.
  • list_orderstrade / portfolioYour orders, filterable by ticker/status.
  • place_ordertrade / portfolioPlace a limit order (yes/no, buy/sell).
  • cancel_ordertrade / portfolioCancel an order's remaining quantity.

FAQ

Will I need an API key?

No gateway key is planned. Once live, you will sign in with OAuth and the client will keep the session.

Which agents will be supported?

Any MCP client that supports remote streamable HTTP should be able to connect once the gateway is deployed.

Can an agent place trades?

Once deployed, yes if you grant the trade scope. During beta, activity uses test Dots with no monetary value. Grant read-only if you only want analysis.

How do I revoke access?

Revoke the connection from your majjha settings (or your MCP client). Tokens can be invalidated server-side.

PreviousWebSocketNext Specifications