Skip to main content

Admin MCP

Run your MintMCP organization from the same MCP client your team already uses. The Admin MCP exposes MintMCP's admin operations as tools, so you can install a connector, write a guardrail rule, or invite a teammate in plain language from Claude Code, Cursor, or ChatGPT — without opening the dashboard.

Because every action runs as you, the Admin MCP enforces the same permissions as the dashboard and writes the same audit trail, so an AI assistant can only do what your role already allows.

What you can do​

Onboard a new organization​

Ask the assistant to get you started and it inspects your org — which servers are installed, whether you've invited your team — and walks you through remaining setup steps with live links into the dashboard.

"Help me get my MintMCP organization set up."

Browse and install MCP servers​

Search the MintMCP catalog, see what a connector needs before you commit, and install it — or add an MCP server that isn't in the catalog by URL. New servers default to admin-only access until you choose to roll them out to the whole organization.

"Install the GitHub connector, but keep it admin-only for now." "Add the remote MCP server at https://mcp.example.com and make it available to everyone."

Deploy and operate hosted connectors​

Build and ship MCP servers that MintMCP runs on its own infrastructure: push a container image, deploy it, set environment variables, check runtime status, and restart when needed. Secrets never pass through chat — the assistant hands you a browser link to enter them.

"Deploy this Dockerfile as a hosted connector and show me its status." "Restart the hosted connector behind our internal-tools server."

Customize what each server exposes​

List the tools a server offers and turn individual tools on or off so your organization only sees the operations you've approved.

"List the tools on our Salesforce server and disable the ones that can delete records."

Govern with rules and middleware​

Create declarative rules that match tool names or prompt text with a regex, or write custom JavaScript middleware for logic a pattern can't express — allowlists, masking, or programmatic checks. Test a rule against sample inputs before it goes live, and roll back middleware to a previous version from the history.

"Block any tool call that runs kubectl get secrets and tell me if it would have caught these three examples." "Write middleware that redacts email addresses from tool responses."

Manage users and roles​

Invite teammates by email with the right role, see which roles are available, and remove people who no longer need access.

"Invite alex@acme.com as an admin and dana@acme.com as a member."

Monitor activity and audit usage​

Get a summary of recent MCP activity, see which users called which servers over any period, and query the call log — tool calls, prompt reads, timing, and status — to investigate a specific incident.

"Which users called our production database server this week?" "Show me failed tool calls on the Slack server in the last 24 hours."

Permissions and audit trail​

The Admin MCP appears in your MCP store as MintMCP Admin, scoped to your organization. Any member can connect to it, but each operation is permission-checked at the moment it runs — if your role can't perform an action in the dashboard, the same action fails here. An assistant connected to the Admin MCP is never more privileged than the person using it.

Every call flows through the MintMCP gateway like any other MCP traffic, so admin actions land in the same activity log and audit trail as the rest of your organization's usage.

Connect to the Admin MCP​

  1. Go to the MCP store in MintMCP.
  2. Open the MintMCP Admin server.
  3. Go to the MCP Client Setup tab and copy the MCP URL.
  4. Add that URL to your MCP client — see Connect Claude Code, Connect Claude on the web, or Connect ChatGPT.