Use ana mcp to connect your AI coding assistant to Anaconda package intelligence. Ana handles the connection settings and installs the Anaconda Intelligence skill for each assistant you select.
The service helps your assistant look up packages, check vulnerabilities, and understand your organization’s channels. It does not install packages or change your environments. For a service overview and other ways to connect, see Anaconda MCP.
Authenticate
Log in with the account that the assistant should use:
If you’re not logged in when you run an MCP command, ana prompts you to log in. For API-key and automation workflows, see Authentication.
Setup saves your API key in each selected assistant’s configuration. Keep these files and their backups private. Do not commit them to version control or include them in support logs.
List clients
To see supported assistants and which ones are configured, run:
This checks for the default anaconda-mcp connection in each assistant’s settings. It does not test the connection or check custom names.
You can also use windsurf in place of devin.
Set up connections
To choose which assistants to connect, run:
Select the assistants you want to use, then restart them after setup. You can also select assistants with command options:
To configure Claude Code and Codex with the current credential, run:
Use --client to update an assistant’s connection after changing accounts or rotating your API key. This replaces its existing entry with the same name. In the interactive wizard, leaving an already configured assistant selected keeps its existing connection; clearing it removes the connection.
For scripts, log in first and specify at least one --client. The --json option changes the output format, not whether setup makes changes.
Keep backups enabled so you can recover existing settings, if needed. Setup backs up configuration files by default, but can replace their contents if they cannot be read. --no-backup skips the new backup; it does not remove old backups.
Installed skills
The Anaconda Intelligence skill helps your assistant use the MCP tools effectively. Setup installs it in the assistant’s skills directory and prints the location. If you’ve edited an existing copy of the skill, save those edits before running setup again, because setup replaces the file without backing it up.
After restarting your assistant, check its MCP connection status to confirm it can reach Anaconda.
Remove connections
Remove the named server entry from selected clients:
To remove a custom-named entry from Cursor, run:
Without --client, ana asks which assistants to disconnect. Scripts must supply --client.
Removing a connection leaves installed skills, backups, and your ana login in place. It does not revoke the API key. To end access for every copy of a key, revoke it in API key management, then update any assistants that still need access. 
