MCP Server + Maintouch
Connect any remote MCP server and give Agent M its tools.
Overview
Your team may already run an MCP server for an internal API or a tool Maintouch does not connect to natively.
Add its URL and Maintouch discovers its tools, so Agent M can call them in chat and in your custom agents. Each server’s tools are prefixed with the name you give it, so two servers never collide.
How it works
- 01
Add a server
Give it a name and paste its MCP endpoint URL.
- 02
Choose how it signs in
No auth, a bearer token, a custom header, or OAuth sign-in. Tokens are encrypted at rest.
- 03
Test and review tools
Maintouch connects, lists the tools it found, and flags the server if it cannot reach it.
What you get
Several servers, one place
Connect more than one server, each with its own name, URL and auth.
Four ways to authenticate
Open servers, bearer tokens, custom headers like X-Api-Key, or a full OAuth sign-in flow.
Guarded network access
Maintouch refuses private and internal addresses, re-checks every redirect, and requires HTTPS for OAuth servers.
Bounded tool lists
Up to 64 tools per server. Oversized tool definitions are trimmed or skipped, so one server cannot crowd out the rest.
Questions
Do you support local (stdio) MCP servers?
No. Maintouch connects to remote servers over streamable HTTP, so your server needs a public URL.
Who can add a server?
Org admins. A server is an org-level connection, so its tools are available in everyone’s Agent M chats.
What if my server is slow or down?
Maintouch gives each connection 8 seconds. A server that fails to load is skipped for that turn, and Agent M carries on with its other tools.