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
Semantic search across organizational memory, indexed claims, and session transcripts.
Exact excerpt retrieval from memory files with configurable scope.
Create a new evidence-backed claim in the tenant's ACTA memory.
Retrieve a specific claim by ID with full evidence context.
Verify a claim's evidence chain, signature, and schema compliance.
Declare an organizational intent with context and evidence expectations.
Compile relevant context for an operation from memory, claims, and intents.
Set an exclusion to prevent specific claims from being surfaced in context.
List detected contradictions between claims in the tenant's memory.
Export an evidence package for independent verification.
Retrieve a cryptographic state root for a specific point in time.
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
Access requires an ACTA account with an API key. OAuth flow authenticates the connection.
All operations are scoped to the authenticated tenant. No cross-tenant data access is possible.
Read operations (search, get, compile) are available to all authorized users. Write operations (create, declare, set) require write-scoped API keys.
MCP access respects the tenant's evidence visibility configuration. Private evidence is never exposed through MCP to unauthorized parties.