The Arcanna MCP server allows user to interact with Arcanna's AI use cases through the Model Context Protocol (MCP).
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"arcanna-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Arcanna MCP Server The Arcanna MCP server allows user to interact with Arcanna's AI use cases through the Model Context Protocol (MCP). ## Usage with Claude Desktop or other MCP Clients #### Configuration Add the following entry to the `mcpServers` section in your MCP client config file (`claude_desktop_config.json` for Claude Desktop). ### Use docker image (https://hub.docker.com/r/arcanna/arcanna-mcp-server) or PyPi package (https://pypi.org/project/arcanna-mcp-server/) ### Building local image from this repository #### Prerequisites - Docker - https://docs.docker.com/engine/install/ #### Configuration 1. Change directory to the directory where the Dockerfile is. 2. Run ```docker build -t arcanna/arcanna-mcp-server . --progress=plain --no-cache``` 3. Add the configuration bellow to your claude desktop/mcp client config. ```json { "mcpServers": { "arcanna-mcp-server": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "ARCANNA_MANAGEMENT_API_KEY", "-e", "ARCANNA_HOST", "arcanna/arcanna-mcp-server" ], "env": { "ARCANNA_MANAGEMENT_API_KEY": "<ARCANNA_MANAGEMENT_API_KEY>", "ARCANNA_HOST": "<YOUR_ARCANNA_HOST_HERE>" } } } } ``` ## Servers One package, three MCP servers. Install once; each executable is a separate server, so a client attaches only what it needs. All three use the same environment (`ARCANNA_HOST`, `ARCANNA_MANAGEMENT_API_KEY`, optional `ARCANNA_AGENTS_HOST`, `TRANSPORT_MODE=stdio|sse`, `PORT` for sse). Tools are filtered by the API key's scopes. | Executable | MCP name | Covers | |---|---|---| | `arcanna-mcp-server` | `arcanna` | Jobs, integrations, events, feedback, buckets, metrics, IaC, roles, platform, code blocks | | `arcanna-agents-mcp` | `arcanna-agents` | Agentic workflows: create, update, run, human-in-the-loop sessions | | `arcanna-rag-mcp` | `arcanna-rag` | RAG documents, collections and tags | Docker…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.