AI Agents
DeepSeek
DeepSeek's assistant, on the web and in its apps.
- Connects with
- Sign in, API key
- Connector
- SPREVA
- Plans
- The DeepSeek API, paid by usage.
Before you start
- Claude Code installed.
- A DeepSeek API key, from DeepSeek's developer platform.
Set it up
- 1
Point Claude Code at DeepSeek's Anthropic-compatible API, with your DeepSeek API key:
Terminal export ANTHROPIC_BASE_URL=https://api.deepseek.com/anthropic export ANTHROPIC_AUTH_TOKEN=sk-... - 2
Add SPREVA:
Terminal claude mcp add --transport http --scope user \ spreva https://dev-app.spreva.ai/api/mcp - 3
Start Claude Code with
claude, run/mcp, choose spreva and sign in. Your browser opens SPREVA: choose the workspace and click Allow.
Also works with
- API key in a header
Send a SPREVA API key as a Bearer token, for automation that runs without a person.
Terminal export SPREVA_API_KEY=POST_API_KEY_... claude mcp add --transport http --scope user \ spreva https://dev-app.spreva.ai/api/mcp \ --header "Authorization: Bearer $SPREVA_API_KEY"
Check it works
Start a new conversation and ask:
What's going out this week on SPREVA?
Claude Code calls SPREVA's overview tool and answers, on DeepSeek's model, with the workspace's time zone, what goes out next and anything that needs attention. The first time, Claude Code may ask you to allow the tool.
Good to know
- While these variables are set, Claude Code answers with DeepSeek's models. Remove them to go back to Claude.
- DeepSeek's guides cover other agents too, such as OpenClaw. Set one up for DeepSeek, then add SPREVA as on the OpenClaw page.
Troubleshooting
/mcp shows spreva as failed
Sign in again from /mcp. If it still fails, check the URL with claude mcp get spreva.
Something else? Troubleshooting covers sign-in loops, plans, limits and time zones.