Connect business tools and MCP
On this page
Let agents retrieve context from messages, tickets and documents without manually copying everything into a prompt.
Before you start
Choose the workspace and the service account you intend to connect. Settings are called Armoury; integrations are also called Alliances. A service account here means the account used for that connection, not necessarily a cloud service-account credential.
Connect a built-in service
- Open Armoury → Integrations in the intended workspace.
- Enable and expand the relevant card: for example Jira, Slack or Gmail.
- Follow its authentication flow or configuration fields. Google Workspace setup has a guided route for Drive, Docs, Sheets, Slides and Calendar access.
- Check the connected status and use the provider's connection check where offered.
- Launch or refresh a supported agent session and ask it to perform a small read operation.
Find the Jira issue APP-123 and the Google document named “Settings redesign”. Summarise the agreed requirements and cite the source items. Keep this task read-only.
Add another service
For Linear or another service, obtain a compatible MCP server's documented command or endpoint and its authentication requirements from that provider.
- Open Armoury → Tools & MCP → Add server.
- Give it a name and select Local command or Remote URL.
- Fill in the command/arguments or endpoint/protocol and required configuration.
- Choose the workspace scope and the tools to expose. Enable Propagate to agent configs where appropriate.
- Review the configuration preview and click Inscribe to save.
- Check the supported agent's tool list and make a small read request against the intended account.
The current MCP Test connection control may show cached discovery counts. Verify a real tool request before treating the connection as working.
Try a public documentation connection
Microsoft Learn provides an official documentation connection that does not require an account. In Add server, name it microsoft-learn, choose Remote URL, enter https://learn.microsoft.com/api/mcp and keep HTTP selected. Leave the headers empty.
Choose Selected workspaces → + Current workspace, keep Propagate to agent configs enabled, review Raw preview, then click Inscribe. Launch a new agent in that workspace and make a small read request:
Use the Microsoft Learn connection to find an official guide explaining Python virtual environments. Read the source through that connection. Return the article title, its link and two brief setup steps. Keep this read-only.
Check that the agent actually uses the new connection and returns a source link. This public-documentation example does not connect your private Microsoft 365 account; services containing your work data have their own authentication steps.
Reuse instructions
Save repeated roles and operating instructions as Minions. For a provider-native skill, use that agent's supported skill mechanism. Shared MCP configuration and provider skills solve different parts of setup; Code Overlord does not document an identical counterpart to every Orca skill-sharing feature.
Check the result
The agent should identify the service and return an actual source item. If it cannot, check the workspace scope, selected account, authentication and per-agent tool visibility. Request write actions explicitly when the workflow needs them.