> ## Documentation Index
> Fetch the complete documentation index at: https://docs.beliefstate.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP integration

> Connect an OAuth-capable AI client to read-only research tools.

Choose the path your client supports. Browser sign-in is available to approved clients; coding clients can also connect with an API key.

<CardGroup cols={3}>
  <Card title="Explore docs" icon="book" href="#documentation-for-agents" cta="Browse public docs" arrow>
    Search public integration guides without a key. No investor records.
  </Card>

  <Card title="Sign in" icon="right-to-bracket" href="#connect" cta="Connect account" arrow>
    Authorize a supported AI client in your browser.
  </Card>

  <Card title="Use an API key" icon="key" href="/introduction#configure-a-coding-client-with-an-api-key" cta="Configure API key" arrow>
    Add a Bearer key to an HTTP MCP client.
  </Card>
</CardGroup>

## Connect

OAuth-capable clients use one public endpoint and browser sign-in. Open registration remains fail-closed until the public admission gate passes.

```text theme={null}
https://beliefstate.ai/mcp
```

[Check current client availability](https://beliefstate.ai/connect) before signup or payment. Public directory listings and OAuth access differ by client. If your AI cannot connect, stop before paying.

For a trusted coding agent that can use HTTPS and store a secret, give it this prompt:

```text theme={null}
Set up BeliefState in this AI using https://beliefstate.ai/auth.md. Send me the full claim link and code. I’ll approve and pay if needed in my browser. Finish the connection and verify a cited answer. Tell me before payment if this AI can’t connect.
```

Approve account access and any payment in your browser. [Configure Codex, Claude Code, Cursor, or OpenCode with an API key](/introduction#configure-a-coding-client-with-an-api-key) if you prefer to set up MCP yourself. [Manage an existing connection](https://beliefstate.ai/account/connections) in your account.

## How it works

The client discovers authorization metadata, the user signs in on BeliefState, and the approved client receives a revocable read-only grant.

* No BeliefState SDK is required.
* All admitted clients use the same remote Streamable HTTP endpoint.
* MCP tools use the same read services, release gates, pricing policy, and append-only usage ledger as REST.
* Client compatibility and provider approval are verified separately.

## Verify

The agent verifies its own response: requested ticker, data mode, coverage warnings, and citations. Report missing access or coverage as a blocked step; a configured server alone does not prove a useful result.

```text theme={null}
Verify BeliefState using the company from my question. Check released coverage, discover available tools, and call get_brief with that company's ticker. If this is only a connection test and no company was requested, select a ticker from current coverage and label it as a test. Return the actual ticker, data_status.mode, warnings, citations, and explicit unknowns. Report missing coverage or access without substituting another company or claiming setup succeeded.
```

## Documentation for agents

Give your coding agent current API references and integration guides without an API key or sign-in. Add this public documentation endpoint to an MCP-compatible client.

```text theme={null}
https://beliefstate.ai/docs/mcp
```

* `search_docs` (Read only). Search current BeliefState guides and API references. Returns ranked pages with short excerpts.
* `read_docs` (Read only). Read current docs as Markdown: supply path and optional section (heading or anchor), or pages for up to 8 reads in one call. Search anchors also work as URL fragments. Unknown selections return per-page errors. Responses are bounded to 120,000 characters; request sections for larger batches.
* `submit_docs_feedback` (Records feedback). Report whether one documentation page was useful, with an optional concise correction or missing detail.

Your client can also read every public documentation page and the published agent skills as Markdown resources. The documentation server provides no investor records. Use the authenticated intelligence endpoint above for investor queries.

* [View documentation tool schemas](https://beliefstate.ai/.well-known/mcp/docs-server-card.json)

## Automatic discovery

Find both MCP endpoints and their authentication requirements from one public document. Clients that support this discovery convention can locate the servers from the BeliefState site URL.

```bash theme={null}
curl --fail-with-body "https://beliefstate.ai/.well-known/mcp"
```

The discovery document defaults to public documentation and lists the intelligence endpoint with OAuth authentication. It is also available at [/.well-known/mcp.json](https://beliefstate.ai/.well-known/mcp.json). The documentation card includes tool descriptions, input schemas, bounds, and read/write annotations from the running server's definitions. Discovery does not grant access or change client admission requirements.

* [View MCP discovery](https://beliefstate.ai/.well-known/mcp)
* [View both server cards](https://beliefstate.ai/.well-known/mcp/server-cards.json)

## Security

Leave passwords, consent, workspace selection, and provider-admin approval with the user.

> An AI must never ask for the user's password, session, OAuth access token, or developer API key.

## Agent feedback

Report unclear, stale, or incorrect documentation through [BeliefState support](https://beliefstate.ai/contact). Include this page URL and the smallest reproducible detail.

*Last updated: 2026-09-27 · API version: v1 (Latest) · OpenAPI publication: 2026-09-13.*


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.