Connect with MCP

The MCP endpoint is https://api.sentinetapp.com/mcp and uses Streamable HTTP. Supply a personal token in the Authorization header. No vendor-specific client is required.

Configure a client

If your client accepts an MCP server configuration, add an HTTP server with this shape. Replace YOUR_SENTINET_TOKEN using your client’s credential or environment-variable support; interpolation syntax varies by client.

{
  "mcpServers": {
    "sentinet": {
      "type": "http",
      "url": "https://api.sentinetapp.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_SENTINET_TOKEN"
      }
    }
  }
}

The server is stateless: clients initialize over HTTP and send protocol messages to the same URL. It does not provide a long-lived GET event stream. Browser pages cannot connect directly.

Available tools

Tool	Permission	Use
get_quote	market:read	Read an instrument’s quote
get_fundamentals	fundamentals:read	Read latest fundamentals
search_tickers	market:read	Find symbols by name or ticker
list_watchlists	watchlists:read	Read your watchlists

MCP tools are read-only. Your client sees only tools allowed by both the released catalogue and your token’s scopes. Administrators may see additional tools. Your account’s plan and the token’s request limits still apply.

Troubleshoot a connection

Check the endpoint, transport and Authorization header first. If the client connects but shows no tool for a resource, check that token’s read permissions. For 401, expiry or revocation, create a replacement token and update the client configuration. For 429, wait as instructed by Retry-After. See authentication and HTTP errors.