/.default`.
* **OAuth Client ID** and **OAuth Client Secret** — both required when M2M is on.
{% endstep %}
{% step %}
#### Continue
Select **Next**. There's no authorization step: the agent requests its own token each time it connects. Choose the tools, then **Create Connection**.
{% endstep %}
{% endstepper %}
With M2M on, the form hides the Redirect URL, because this grant never redirects anyone. If Token URL, client ID or client secret is missing, the form says which one, for example *Token URL is required for the client credentials grant*, and doesn't continue.
If a server expects client credentials and you connect it without M2M, the connection can look successful while every tool call fails as unauthorised. Turn M2M on and reconnect.
### Managing a connection
Open an existing connection to see **MCP Server Connection**: the connection's name and URL, and under **Tools and Settings**, its enabled tools with a count such as `4 tools enabled` and a search box.
| Action | What it does |
| ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Connect** / **Disconnect** | Turns the connection on or off. Disconnecting asks first: *Disconnecting will stop all ongoing sessions using this MCP server.* |
| **Remove** | After a confirmation, permanently removes the MCP server from the agent. |
| **Initialize** | Shown instead of Connect when the connection has no credentials yet, such as one imported without its MCP configuration. Reopens Create MCP Connection with the name and URL filled in. |
| Edit (pencil) | Reopens Create MCP Connection with the saved name, URL, client ID, headers and M2M settings filled in. |
| **Manage Tools** | Opens **Manage Tools and Settings**: turn tools on or off with **Enable All** or each switch, change supervision modes, rewrite descriptions, and select **Refresh tools** to fetch the server's current list. Then **Save Changes**, or **Back**. |
{% hint style="info" %}
**Re-enter the client secret when you edit.** The secret isn't shown again after saving, so editing a connection that uses one means typing it again.
{% endhint %}
### Exporting and importing
[Export Agent](/ai-workbench-qore/console/agent-builder/deploy/export-agent.md) always includes the agent's MCP connections. **Include MCP configuration**, off by default, decides whether their OAuth client ID and secret, headers and tokens go too. Connections exported without it arrive in the other environment needing **Initialize**.
### Where connected MCPs show up
* **The canvas:** each connection appears as a node in the Skills band, labelled with the connection's name.
* [Skills & Capabilities](/ai-workbench-qore/console/agent-builder/build/skills-and-capabilities.md): the server's enabled tools.
* [Connectors](/ai-workbench-qore/control-center/govern/connectors.md) › **MCP Servers**, in Control Center: one row per connection in the account, with its project and the agent that uses it.
### MCP Tools compared to Apps & Services
Both add outside capability to the agent, and the catalogs overlap.
* [Apps & Services](/ai-workbench-qore/console/agent-builder/build/apps-and-services.md) lists SaaS connectors, such as Stripe, Resend and Twilio, connected through the Integrations Hub.
* MCP Tools lists MCP servers, such as market-data, web-scraping and knowledge-retrieval services. The **MCP Server** skill reaches any other MCP server by URL.
* For an HTTP endpoint that isn't an MCP server, use the [API Call](/ai-workbench-qore/platform-resources/skill-library/api-call.md) skill.
***
{% columns %}
{% column width="83.33333333333334%" %}
Maintained by Abhishek Paul
AI-assisted, human-approved
{% endcolumn %}
{% column width="16.666666666666664%" %}
{% endcolumn %}
{% endcolumns %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.uptiq.ai/ai-workbench-qore/console/agent-builder/build/mcp-tools.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
