Developers

ACTA MCP / Claude

Connect Claude to ACTA through the Model Context Protocol. 12 tools, stdio and HTTP transport, OAuth/account gating, and tenant-scoped read/write access.

12 MCP Tools

memory_search

Semantic search across organizational memory, indexed claims, and session transcripts.

memory_get

Exact excerpt retrieval from memory files with configurable scope.

claim_create

Create a new evidence-backed claim in the tenant's ACTA memory.

claim_get

Retrieve a specific claim by ID with full evidence context.

claim_verify

Verify a claim's evidence chain, signature, and schema compliance.

intent_declare

Declare an organizational intent with context and evidence expectations.

context_compile

Compile relevant context for an operation from memory, claims, and intents.

exclusion_set

Set an exclusion to prevent specific claims from being surfaced in context.

contradiction_list

List detected contradictions between claims in the tenant's memory.

evidence_export

Export an evidence package for independent verification.

state_root_get

Retrieve a cryptographic state root for a specific point in time.

answer_cache_query

Query the answer cache with evidence provenance tracking.

Connection Modes

stdio

Local process communication. Claude Desktop connects directly to the ACTA MCP server process.

{"mcpServers": {"acta": {"command": "acta-mcp", "args": ["--tenant", "your-tenant"]}}}

HTTP

Remote HTTP transport. Connect to a hosted ACTA MCP endpoint with OAuth authentication.

{"mcpServers": {"acta": {"url": "https://acta.ardyn.ai/mcp", "auth": "oauth"}}}

Authorization Model

OAuth / Account Gating

Access requires an ACTA account with an API key. OAuth flow authenticates the connection.

Tenant Scoping

All operations are scoped to the authenticated tenant. No cross-tenant data access is possible.

Read/Write Policy

Read operations (search, get, compile) are available to all authorized users. Write operations (create, declare, set) require write-scoped API keys.

Evidence Visibility

MCP access respects the tenant's evidence visibility configuration. Private evidence is never exposed through MCP to unauthorized parties.

← Developers