Arcane MCP
by jmagar
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Pino log level: trace, debug, info, warn, error | info |
| ARCANE_API_KEY | Yes | API key from Arcane Settings > API | |
| ARCANE_API_URL | Yes | Base URL of your Arcane instance, e.g. https://arcane.example.com | |
| ARCANE_MCP_PORT | No | Host-side Docker port mapping | 44332 |
| ARCANE_MCP_TOKEN | Yes | Bearer token for MCP server auth. Generate with: openssl rand -hex 32 | |
| ARCANE_MCP_BIND_PORT | No | Internal container port the server binds to | 3000 |
| ARCANE_MCP_TRANSPORT | No | Transport mode: http or stdio | http |
| ARCANE_MCP_ALLOW_YOLO | No | true skips elicitation prompts; re-call with params: { confirm: true } is still required | false |
| ARCANE_MCP_AUTH_ENABLED | No | Set to false to disable Bearer auth (use only behind a trusted proxy) | true |
| ARCANE_MCP_ALLOW_DESTRUCTIVE | No | true auto-confirms all destructive operations. Use only in fully trusted automated environments. | false |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/jmagar/arcane-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server