The remote server gives you the full Annie experience: infrastructure investigation, log analysis, incident debugging, and more. It replaces the need for a locally running MCP server.
Setup
One-command install
Install across all your editors at once using add-mcp:Manual configuration
Add to your editor’s MCP config file (e.g..cursor/mcp.json, ~/.claude.json, claude_desktop_config.json):
First Use
On your first Annie tool call, your editor will open a browser window:- Log in with your Anyshift account
- The connection is established automatically
- No tokens to copy — your editor stores the credentials
Available Tools
| Tool | Description |
|---|---|
ask_annie | Ask a question about your cloud infrastructure |
get_annie_response | Poll for Annie’s answer (called automatically by your editor) |
list_projects | List your Anyshift projects |
set_project | Switch the active project for queries |
Example Prompts
Managing Access
You can view and revoke authorized MCP connections from your profile page under Authorized Apps.Troubleshooting
Re-authenticate
Re-authenticate
If your session expires, reset the connection and try again:Your next Annie tool call will re-open the browser for login.
Browser doesn't open during auth
Browser doesn't open during auth
Make sure your default browser is set in your OS settings. If using a remote/SSH session, you may need to use the local stdio server instead.
Timeout waiting for response
Timeout waiting for response
This is normal — Annie is still working. The
get_annie_response tool is called automatically by your editor until the answer is ready. Complex investigations can take a few minutes.