API keys
Org-scoped keys for the findry-mcp context engine: read-only graph access for Claude Code, Cursor, or any MCP client. Keys are hashed at rest and shown exactly once at mint time; every mint and revoke is audited. Revoking takes effect on the key's very next use.
Mint a key
Name the place the key will live (a laptop, a CI job, a shared agent host) so the audit trail reads plainly.
Keys
Connect an MCP client
Substitute a stored key for the fdy_ placeholder. Every tool result carries the honesty vocabulary (trusted vs candidate, confidence, evidence ids, verified-as-of), and the server is structurally read-only.
Authenticate with an API key: mint one in the card above (it is shown once), then substitute it for the placeholder. Full transport and tool reference in docs/MCP.md.
{
"mcpServers": {
"findry": {
"type": "http",
"url": "https://mcp.findry.ai",
"headers": { "Authorization": "Bearer fdy_<your key>" }
}
}
}{
"mcpServers": {
"findry": {
"type": "http",
"url": "https://mcp.findry.ai",
"headers": { "Authorization": "Bearer fdy_<your key>" }
}
}
}claude mcp add --transport http findry https://mcp.findry.ai \ --header "Authorization: Bearer fdy_<your key>"
Local development (developing Findry itself)
Build the server binary once: cd core && go build -o ../bin/findry-mcp ./cmd/mcp. The stdio server reads the local dev database; its DSN comes from the compose stack in deploy/, never from this page. A locally running HTTP server (make mcp) listens on http://localhost:8090.
{
"mcpServers": {
"findry": {
"command": "/path/to/findry/bin/findry-mcp",
"env": {
"DATABASE_URL": "<your local dev database, see deploy/docker-compose.yml>",
"FINDRY_MCP_API_KEY": "fdy_<your key>"
}
}
}
}