MCP Servers
MCP servers let Atua connect to tools and services outside the app.
Use them when you want Atua to work with things like Notion, GitHub, Linear, your files, internal docs, databases, or other third-party apps.
What It Feels Like
Once a server is connected, Atua can use those tools while responding to you.
That means Atua can do more than answer questions. It can look things up, pull information from connected apps, and take actions through the tools that server provides.
You will see tool calls in the chat, so you can tell when Atua used one.
Two Kinds Of Servers
Atua supports:
- Local servers, which run on your Mac
- Remote servers, which run somewhere else and connect over the network
Add A Server
- Open Settings > MCP.
- Click +.
- Choose Local or Remote.
- Fill in the details.
- Click Add Server.
Atua will try to connect right away and list the tools it finds.
Remote Servers
Remote servers run somewhere else and connect over the network. Some support OAuth, so you authorize access through your browser instead of managing API keys.
Example: Notion
Notion has an official MCP server. Here is how to add it:
- Open Settings > MCP.
- Click + and choose Remote.
- Enter the details:
| Field | Value |
|---|---|
| Name | Notion |
| URL | https://mcp.notion.com/mcp |
- Click Add Server.
- Atua opens your browser to authorize Notion. Pick the workspace and pages you want Atua to access, then confirm.
- Once authorized, Atua connects and shows the available Notion tools.
That is it. No API keys, no tokens to paste. OAuth handles the connection.
Local Servers
Local servers run on your Mac. You give Atua a command to start them.
For a local server, you usually need:
- A name
- A command to run
- Any arguments that command needs
- Optional environment variables
Example:
| Field | Value |
|---|---|
| Name | Filesystem |
| Command | npx |
| Arguments | @modelcontextprotocol/server-filesystem /Users/me/Documents |
If npx is not found, try the full path instead.
Manage Tools
Each connected server shows its tools in the Tools section.
You can turn individual tools on or off. This is helpful if a server offers many tools and you only want a few of them available.
Use Refresh Tools if the server changed and you want Atua to reload the list.
Use MCP Tools With A Command
You can give a specific command access to only certain MCP tools:
- Open Settings > Commands.
- Select a command.
- Open the Tools section.
- Turn Enable Tools on.
- Choose the tools you want that command to use.
If you turn tools on but do not pick specific ones, the command can use all available tools.
Shared Commands And MCP Servers
When you export a command that uses MCP tools, Atua can include the matching MCP server definition in the shared JSON bundle.
When someone imports that bundle:
- Atua detects which MCP servers the command depends on
- It asks whether the missing server should be added
- If the server is added, Atua enables the MCP tools required by that command
This makes it easier to share commands like “Bookmark to Notion” without asking someone to rebuild the command by hand.
Sensitive data is not included in shared bundles. That means:
- OAuth tokens are not shared
- Client secrets are not shared
- Custom header secrets are not shared
- Environment variable secrets are not shared
If the imported MCP server needs authentication, the user still has to authorize it on their own Mac.
Turn A Server Off
Use the Enabled toggle in a server’s detail view to connect or disconnect it.
Atua reconnects to enabled servers when the app starts.
Find Servers
Good places to look:
- MCP Server Registry
- Product docs for tools you already use
Many servers can run with npx, so you often do not need a full install.
Troubleshooting
Server will not connect
- Make sure the command or URL is correct
- Check any required API keys or environment variables
- For local servers, try running the command in Terminal first
Tools do not appear
- Wait a few seconds, then click Refresh Tools
- Check the server’s own setup guide
Atua is not using the tools
- Make sure the server is connected
- Make sure the tools are turned on
- If you are using a saved command, make sure Enable Tools is on for that command
- If the command was imported, check that you approved the MCP server install during import