Listaro Docs

Connect an MCP client

Remote Streamable HTTP, workspace consent, scoped keys, and revocation.

Remote endpoint

Open MCP connections and copy your application's endpoint ending in /mcp. Use a client supporting remote Streamable HTTP. The server supports the modern per-request protocol and the stateless 2025 transport.

OAuth connection

Add the endpoint to your client and choose OAuth sign-in. Listaro opens a consent page identifying the application, its registered return address, and requested identity access.

Choose one workspace and only the tools the client needs. Approval uses the provider's authorization-code flow with PKCE. The client receives its own access token; it does not receive your account session.

Connections cannot manage account settings or use the database directly. Current membership and selected scopes are checked on every request. Revoke a connection from MCP connections to block existing access and refresh.

Identity scopes such as openid, email, and profile describe identity data. Listaro tool permissions are selected separately at consent.

API key connection

Clients supporting a private Authorization header can use Bearer YOUR_LISTARO_API_KEY. Create a key with the exact required tool scopes in API keys. Keep it out of shared client configuration and screenshots.

Execution and retries

Supply idempotencyKey in an execution tool's arguments. Retain the same key and arguments after an uncertain response. Use a new key for a new operation. HTTP clients may also supply the Idempotency-Key header.

Tool discovery requires authentication and lists only permitted tools. Account cookies are not accepted as MCP credentials. The endpoint does not require persistent server sessions.

Troubleshooting

  • Sign-in required: start again from your client to obtain a fresh authorization request.
  • Scope denied: reconnect and approve the necessary tool, or ask a workspace administrator to review your role.
  • Connection revoked: approve a new connection from the client.
  • Engine unavailable: the commercial gateway is reachable, but the separately configured capture engine is unavailable.
  • Origin rejected: browser-based clients require an explicitly permitted origin; desktop and server clients normally omit browser Origin headers.

Client directory submissions and platform approval are separate from a working transport.

On this page