Unable to Fetch MCP Tools When Adding MCP Tool to AI Agent
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello Community,
We are working on a use case where one ServiceNow instance functions as the MCP server and another as the MCP client. On the MCP server instance, we configured both the default QuickStart MCP Server and a custom MCP server through the MCP console. As part of the setup, we also created an OAuth inbound integration and configured the corresponding client settings on the MCP client instance, following the steps provided in the ServiceNow documentation.
The client is able to authenticate with the server successfully, and the MCP execution logs confirm successful responses. However, when attempting to add an MCP tool to our AI Agent, we consistently receive the error message “Unable to fetch the tools for the MCP server.”
We have reviewed the configuration on both the client and server instances and verified that the MCP client and MCP server plugin versions match on both environments. Additionally, both instances are running on the same patch level:
glide‑zurich‑07‑01‑2025__patch4‑hotfix3‑12‑23‑2025.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
In the client instance, check your MCP server execution logs [sn_mcp_execution_logs] for clues. There should be a table for this in the platform schema. I am unsure if you have checked both client and server logs.
You can also turn on Flow Reporting for the MCP client artifacts:
Flows:
MCP with Streaming - Subflow
MCP Without Streaming - Subflow
Action Type:
MCP POST (with Streaming)
MCP POST (without Streaming)
MCP token validation
MCP Tool Executor
Disconnect with MCP server
After attempting to retrieve Tools, go view your Flow Executions and review any error detail there as well.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Wednesday
I'm getting the same issue, tried an out of box and custom MCP server and this is what I get for boths in the logs
{"protocolVersion":"2025-06-18","clientInfo":{"version":"1.0.0","name":"Servicenow","title":"Servicenow"},"capabilities":{}}
