Use Starko from Claude, Cursor and VS Code
Use Starko from Claude, Cursor and VS Code
Starko turns what your customers tell you into shipped product improvements. With the Starko MCP server, you can do that work from the AI tools you already use: ask Claude what customers are reporting, turn a request into a ticket, send it to Starko AI, and merge the result, without leaving the conversation.
What you can do
Once connected, your AI assistant has the same tools as the Starko chat:
- See what customers are asking for. Search tickets and conversations, read the full context, find what is urgent, overdue or about to breach an SLA.
- Understand who it matters to. Look up the client, company, tenant and deal behind a request.
- Turn requests into work. Create tickets with the request as the brief, group them into projects, link what blocks what.
- Send it to the factory. Start a Starko AI run on a ticket, follow the session, answer the agent's questions, and merge the pull request it opened.
- Close the loop. Reply to the customer, update the knowledge base, build a workflow so the next request handles itself.
Everything happens as you: the assistant signs in with your Starko account and works with your role in the workspace you choose. It sees what you can see and nothing more.
Before you start
A workspace owner has to switch MCP access on once, under Settings → Connections → Starko MCP server. The same panel shows the endpoint and the one-line command for Claude Code.
Connect from Claude
Claude.ai or the Claude desktop app
- Open Settings → Connectors and choose Add custom connector.
- Name it Starko and paste the endpoint:
https://v2.starko.one/api/mcp. Leave the client id and secret empty. - Click Connect. Starko opens: sign in if needed, pick the workspace the connection may work in, and click Allow access.
- In a chat, open the tools menu and enable the Starko connector.
Claude Code
Then run claude, type /mcp, pick starko and choose Authenticate. The same Starko consent screen opens in your browser.
Connect from Cursor or VS Code
Add a custom MCP server of type HTTP (sometimes called Streamable HTTP) with the URL https://v2.starko.one/api/mcp. The editor discovers that Starko uses OAuth and sends you to the consent screen the first time you use a tool. No API key is needed, and there is none to create.
How approvals work
Reading is instant. Anything with consequences, such as closing or archiving tickets, replying to a customer, changing a CRM record or starting a Starko AI run, never runs on the first call. Starko answers with a plain summary of what would happen, your assistant shows it to you, and only after you agree does the action run, exactly once.
This is the same rule the Starko chat follows with its approval cards; the assistant just carries the question to you.
One connection, one workspace
A connection is bound to the workspace you picked when you allowed access. If you work in two workspaces, add the connector twice under two names.
Permissions and revoking access
- Your assistant acts with your role. Owners and admins can start Starko AI runs and merge pull requests; members get the tools their role allows.
- If you are removed from the workspace, every connection you made to it stops working at once.
- To end a connection, remove or disconnect the connector in the app you added it to. The owner can also switch MCP access off for the whole workspace in Settings → Connections.
Troubleshooting
- The consent screen says the app could not be verified. The app you are connecting from is not one Starko recognises. Connect from Claude, Cursor or VS Code, or use their latest version.
- "MCP access is switched off for this workspace." Ask a workspace owner to enable it under Settings → Connections.
- Tools are missing. You see only the tools your role allows, and some tools appear only in workspaces that configured them (for example the Pantheon ERP tools).
- An action asked for approval twice. Each approval is valid for ten minutes and can be used once; if you waited longer or the assistant changed the arguments, it asks again.
Technical details, including the full tool list, are at .
Did this answer your question?