Connect AppControler to Cursor

Cursor talks to your AppControler workspace through the Model Context Protocol (MCP). From the Agent or Composer pane you can:

• List discovered apps filtered by risk or AI-only
• Check who authorized a specific app
• Approve, review-flag, or block an app without leaving the editor
• Pull upcoming contract act-by dates into a report or changelog

• An AppControler account with a connected workspace.
• Cursor (any recent version with MCP support).
• An MCP API key — create it in AppControler under Integrations → MCP / API keys. The key is shown once; store it somewhere safe before continuing.

1. 1

   Create an MCP API key

   In AppControler, open Integrations and click Create MCP key. Copy the acp_… key now — it is displayed only once and only a hash is stored server-side.

2. 2

   Open Cursor’s MCP settings

   In Cursor: Cursor Settings → MCP & Integrations → Add Custom MCP server. This opens ~/.cursor/mcp.json (on Windows:%USERPROFILE%\.cursor\mcp.json).

3. 3

   Add the AppControler server

   Replace your key below and save the file:

   {
     "mcpServers": {
       "appcontrol": {
         "url": "https://appcontroler.com/api/mcp",
         "headers": {
           "Authorization": "Bearer acp_YOUR_KEY"
         }
       }
     }
   }

   Use the url + headers shape (HTTP transport), not a command/stdio entry — AppControler is a remote MCP server over HTTPS.
4. 4

   Verify the connection

   Cursor refreshes the MCP list automatically. The appcontrol entry should show a green status and list tools like list_ai_apps and get_policy_summary.

5. 5

   Ask Cursor something

   In Agent mode, try “List the high-risk AI apps connected to our workspace” or “Which renewal act-by dates are coming up in the next 30 days?”

• 401 / Unauthorized — the header must read Bearer acp_… exactly. Check for a missing space, a truncated key, or a revoked key.
• Server stays red — confirm the URL is https://appcontroler.com/api/mcp and reload the MCP list from Cursor settings.
• “This key does not have the write scope” — the key was created read-only. Create a new key with the write scope for policy changes.