What you get
Claude gains live access to your AppControler workspace through the Model Context Protocol (MCP). Ask it things like:
- “List every AI app employees connected to our workspace, highest risk first.”
- “Who authorized ChatGPT with company sign-in?”
- “Summarize our approve / review / block policy counts.”
- “Which contract notice dates land in the next 60 days?”
- “Block the app called Perplexity for us.”
The connection uses OAuth sign-in, so there are no API keys to manage for this path.
Before you start
- An AppControler account with a connected Google Workspace (free plan is fine).
- A Claude account on claude.ai or the Claude desktop app.
- The MCP server URL:
https://appcontroler.com/api/mcp
Connect Claude (step by step)
Add a custom connector in Claude
In claude.ai, open Settings → Connectors and select Add custom connector. Paste the server URL:
https://appcontroler.com/api/mcpKeep “Sign in now” authentication
Under Authentication, choose Sign in now. Each user signs in through AppControler's OAuth flow before the connector can be used.
Choose “Register automatically” for the OAuth client
Under OAuth client, pick Register automatically. Claude registers itself with AppControler — do not paste an MCP API key into the client ID field; keys are a different auth path.
Approve access in the browser
Save the connector. A browser window opens the AppControler consent screen showing the requested scopes. Sign in to your workspace if prompted, then click Approve. You are returned to Claude and the connector turns on.
If the Approve button appears to do nothing, pop-up blockers or a stale tab are usually the cause. Close the window, click “Connect” in Claude again, and complete the flow in the fresh window.Use it in a conversation
Start a chat, make sure the AppControler connector is enabled under the tools menu, and ask your first question, e.g. “List the AI apps connected to our workspace.”
Troubleshooting
- Unauthorized / 401 errors — disconnect and reconnect the connector so a fresh OAuth token is issued.
- Connector added but no tools appear — confirm the URL is exactly
https://appcontroler.com/api/mcpand that you approved the consent screen. - Tools missing write actions — the consent screen granted the scopes you saw. Reconnect and approve both read and write if you want policy changes from chat.
FAQ
Do I need an AppControler API key to connect Claude?
No. Claude custom connectors use OAuth sign-in, so you approve access with your AppControler account instead of pasting a key. API keys are for clients that set a header directly, like Cursor, Claude Code, Windsurf, and n8n.
Which AppControler workspace does Claude see?
The workspace of the account you sign in with on the consent screen. Each team member who connects sees the same organization they belong to in AppControler.
Can Claude change app policies, or only read?
By default the connection gets both read and write tools, so Claude can approve or block an app when you ask it to. You control what you approve on the consent screen, and every action runs against your workspace policy.
How do I disconnect Claude from AppControler?
In Claude, open Settings → Connectors and remove the AppControler connector. This revokes the tokens AppControler issued. Any MCP API keys you created separately stay active until you revoke them in Integrations.
Does this work in the Claude desktop app?
Yes. The Claude desktop app supports the same custom connectors. Open Settings → Connectors there and follow the same steps.
See every AI tool connected to your workspace
Free scan shows the apps employees authorized with company sign-in — before you connect them to AI assistants.
Start free AI scan