MCP Access

Expand the tools your agents have access to.

When running in hosted mode, only Remote MCP Servers are supported. Both remote and STDIO servers are supported when running in CLI mode.

MCP (or Model Context Protocol) servers provide a way to add additional tools to your agents without coding them. There are typically two types of MCP connections - STDIO or local servers and Remote. With STDIO servers you typically pass a command with arguments and the Agent SDK will start the process. Here's an example:

npx -y mcp-remote https://mcp.atlassian.com/v1/sse

Here we're just starting up a local mcp-remote tool that can connect to a remote service and handle's OAuth or other types of authentication.

Connecting to your remote MCP server

The agent SDK provides a tool that is available to every agent. To add a new tool, you just need to ask your agent (this from our snarky sample agent!):

peoplelogic:>q connect a new mcp server
agent:> Alright, before I can get this party started and connect a new MCP server for you, I'll need a few more juicy details: 
- The URL of the MCP server you're dying to connect.
- What kind of connection you want (for yourself or for the whole organization)?
- Is this thing streamable over HTTP or SSE?
- Any authentication needed (bearer token, API key, etc)?

Just let me know these details and, of course, if there's anything else you want to throw in. Once you've handed over the goods, make it clear you're ready to proceed!

You can see that this process is very similar to connecting your HRIS or your ATS. Now you just need to provide the whole URL, whether you want it just for yourself (only admins can add for the whole organization), whether its Streamable HTTP or SSE and then the authentication type.

At the time of writing, the MCP server world is migrating from SSE to Streamable HTTP. Be sure to check the type before connecting.

The agent SDK will then ask you for the actual bearer token or API key and then you'll confirm and you're done!

Running MCP tools in your agents

The MCP tools are integrated into all of your agents just like any other tool. When you send in a new task, the coordinator agent will determine the available tools, whether you have provided all the information, and then send the data to the MCP server. Take a look (this is after connecting the Stripe MCP server):

peoplelogic:>q summarize the pricing of my subscriptions
agent:> Alright, here's the scoop on your Stripe subscriptions pricing:

- Every subscription you have is for the "Pro Monthly" plan, which runs $5.00 per user per month (USD).
- Quantities per subscription vary (so you'll pay $5 times the number of users for each subscription):
  - Subscription #1: 7 users ($35/month)
  - Subscription #2: 1 user ($5/month)
  - Subscription #3: 76 users ($380/month)
  - Subscription #4: 10 users ($50/month)
- There are currently no discounts or fancy coupons attached to these subscriptions.

If you want a total, just add up those amounts and you've got your monthly Stripe bill for all your subscriptions. If you want more details (like billing dates or features), just say the word!
peoplelogic:>

In seconds we've summarized data from our Stripe account, without needing to know the Stripe API or to build a custom tool. Huge time saver!

Managing MCP connections with the CLI

When running in CLI mode, the agent SDK provides several additional commands to make it easier to manage connected applications:

list-connected-app

peoplelogic:>list-connected-apps 
The following apps are active and connected: 
* agent:mcp:http:github (61a60022-2083-40ee-bd82-e89bbbb08225) - MCP app for github (github) 
* agent:mcp:http:stripe (6b7dddd4-5a0b-469f-95e4-594ac3968c72) - MCP app for stripe (stripe) 
* agent:mcp:sse:hubspot (4ca48431-2eff-4991-9a91-41eff702bdaf) - MCP app for hubspot (hubspot) * agent:mcp:sse:octagon_agents (771c972f-2537-415b-a7a6-1c4b12c8a6ee) - MCP app for octagon_agents (octagon_agents)

add-connected-app

add-connected-server --type github --url https://api.githubcopilot.com/mcp/ --authType bearer --accessToken "XXXX"

remove-connected-app

peoplelogic:>remove-connected-app 771c972f-2537-415b-a7a6-1c4b12c8a6ee
Deleted connected app for id 771c972f-2537-415b-a7a6-1c4b12c8a6ee.

Last updated

Was this helpful?