Coming soon

Every MCP server your company uses.
One place to decide who gets what.

Control My MCP sits between your AI assistants and your business systems. Each role gets a single connector with exactly the tools it needs, every call runs as the person asking, and nothing reaches the model that you haven't looked at first.

Talk to TWG Security See what's inside

Claude, ChatGPT, GrokAny client that speaks MCP

Per-user sign-inAttributed, never shared keys

Run in your tenancyHosted or self-hosted servers

app.controlmymcp.com/connectors

Connectors

One connector per role. People connect once from their AI client and get only what their role allows.

Connector	Servers	Groups	Status
Sales	CRMQuotingEmail	Sales reps	Active
Service technician	TicketingCameras+4	Field service	Active
Finance	AccountingCRMEmail	Finance	Active
Project manager	TicketingFleetEmail	PMs	Active
Warehouse	InventoryQuoting	Warehouse	Pending review
After-hours bot	Ticketing	Automation	Token

Role connectors

Give a sales rep the CRM. Give a technician the cameras. Never the other way around.

A connector is one URL a person adds to Claude, ChatGPT or Grok. Behind it, Control My MCP bundles the MCP servers that role is allowed to use, applies the tool rules for their group, and signs them in once.

Sales

Reps and account managers

CRMQuotingEmail & calendarPricing table

Read deals, draft quotes, book meetings. Deal-stage changes stay gated.

Service technician

Field and bench techs

TicketingCamerasAccess controlNetworkDocumentation

Look up a site, pull a snapshot, log time. Device changes need a reviewer.

Finance

Controller and AR

AccountingCRMInvoicing

Match won deals to invoices, chase AR, build the month-end pack.

IT manager

Admins and engineers

Everything abovePlatform control

Add servers, review new tools, restart runtimes and read the audit trail, from the same chat window.

New tools wait in quarantine until a human says yes.

MCP servers change. A vendor ships a new tool, renames one, or quietly rewrites a description to tell the model something it shouldn't do. Control My MCP re-reads every server's contract, diffs it, and holds anything new or suspicious back from every connector until it's reviewed.

Prompt-injection screeningTool descriptions are scanned for instructions aimed at the model, not the user.
Allow and deny per group, per connectorDestructive tools are off by default for non-admin roles. Overrides are explicit and audited.
Annotation honesty checksA tool that claims to be read-only but writes gets flagged before anyone can call it.

app.controlmymcp.com/servers

MCP servers

Hosted, self-hosted from git, or a plain command. Each one is scanned and discovered the same way.

CRM Running

42 tools · hosted · per-user sign-in

Ticketing 2 pending

61 tools · docker from git

Cameras Running

23 tools · docker from git

Access control Sign-in needed

19 tools · hosted · OAuth

Accounting Running

18 tools · command

Documentation Running

4 tools · hosted

Every call has a name on it.

Shared API keys make every AI request look like the same person. Control My MCP signs each user into the upstream system under their own account, so the CRM, the ticketing system and the audit log all see who actually asked.

Per-user OAuth to the upstreamGoogle, HubSpot, Cloudflare and any OAuth-native MCP server. Users connect once from their account page.
A ledger, not a log fileWho, which tool, which AI client, how long it took, what came back. Filter by any of them.
Result inspectionCard numbers, secrets and personal data are masked before the model sees them. Warn, mask, or block, by policy.

app.controlmymcp.com/reporting

Reporting · last 24 hours

Every tool call across every connector, attributed to a person and an AI client.

Tool calls1,284+9%

People23

Masked results31

Errors0.4%

When	Person	Client	Tool	Result
14:02	JEJordan Ellis	Claude	crm.search_deals	ok · 410 ms
14:01	PNPriya Natarajan	ChatGPT	tickets.add_note	ok · 380 ms
13:58	SOSam Okafor	Claude	cameras.snapshot	masked · PII
13:55	JEJordan Ellis	Grok	quotes.create	denied · role

What's inside

Built by an integrator, for the systems integrators actually run.

TWG Security built this platform to run its own business on it first: ticketing, CRM, accounting, cameras, access control, networking and documentation, all reachable from a chat window, all governed in one place. Control My MCP is that platform, made available to other companies.

Run any MCP server

Point at a hosted server, deploy one from a git repository into an isolated container, or wrap a command-line server behind the platform's bridge. OAuth-native servers register themselves on add.

Connectors by role, folders by department

Settings flow down: a folder decides tool exposure, rate limits and inspection policy; a connector can tighten them, never loosen.

Condensed tool exposure

A server with 200 tools becomes four: search, describe, read, write. The model finds what it needs instead of drowning in a tool list, and your context budget stays yours.

Inspection and capture

Mask or block personal data, secrets and credentials in results. Capture full request and response payloads on a connector while you test, then switch it off.

Health, alarms and self-healing

Fleet health across tenants, per-server logs and traffic traces, automatic re-discovery when an upstream session expires, snapshots before every restart.

Multi-tenant from day one

Each customer gets its own tenant, roles, groups and reporting. Operators see the fleet; tenant admins see only their own house.

Launching soon. Talk to the team that already runs it.

Control My MCP is the next chapter of the MCP manager TWG Security uses every day. If you want early access, or you'd like the same setup for your company now, start with a conversation.

Contact TWG Security