MCP
Use MCP when you want an MCP host to call Axisdream as tools.
Axisdream MCP supports both local hosts and hosted remote MCP clients.
It stays aligned with the platform so tool names and descriptions stay current.
For most users, the fastest path is still the Integrations page in the app.
When to use MCP
- Use MCP when the caller is an MCP host.
- Use the hosted MCP URL for web chatbots that support remote MCP with OAuth.
- Use the local wrapper for desktop or CLI tools that launch MCP over stdio.
- Use the SDK when you are writing application code.
- Use REST when you want direct HTTP control.
Fresh-space behavior
- If the selected space is still being set up, the AI asks one setup question before normal work.
- During that first pass, the connection focuses on writing the initial knowledge, memory, and compact state.
- Normal work begins after the initial setup is complete. Template spaces are ready-made starting points.
Hosted MCP
Use this URL in ChatGPT, Claude, Grok, Manus, or another web chatbot that supports remote MCP. The chatbot opens the Axisdream OAuth sign-in and consent flow; do not paste an API key into the hosted connection.
https://axisdream.xyz/mcpLocal MCP
Use this setup for Cursor, Codex, Claude Code, VS Code, OpenClaw, and other hosts that launch a local MCP process. AXISDREAM_SPACE is optional; without it, the connected AI asks which space to use.
export AXISDREAM_API_KEY="cs-YOUR_KEY"
export AXISDREAM_BASE_URL="https://api.axisdream.xyz"
export AXISDREAM_SPACE="optional-preferred-space"npx -y axisdream-mcp@1.0.0Tool surface
Onboarding tool visibility
Normal spaces expose the full Axisdream tool set. Fresh spaces can expose a smaller onboarding-safe subset until the initial context is complete.
Recommended usage
- Without a preferred space, let the agent ask which space to use before space-specific work.
- Set AXISDREAM_SPACE only when you want one preferred starting space; the agent can still switch when you ask.
- Use retrieve first for questions, research, planning, or any work that depends on space knowledge.
- Use list only when you need the file or folder structure; it is not a substitute for retrieve.
- The connected AI handles the search request through retrieve; you do not need to choose a search method.
- Inspect snippets and references first, then use fetch only when you need a complete known file.
- Use list_skills and get_skill for procedural knowledge.
- Use get_related_files when you want the file-level connections already recorded in the space.