Docs · With your agent
Add Vinktar to Replit
At the end Replit’s agent can set Vinktar up in your app and read your analytics and errors.
Before you start
You need a Vinktar workspace. Replit Agent takes MCP servers from the integrations page, and a connected server is available in every one of your projects. Vinktar’s MCP server is a standard Streamable HTTP server with OAuth 2.1 sign-in. Add it the way Replit’s docs describe for any custom server. You paste no key.
1. Add the server to Replit
The steps are the ones in Replit’s documentation, with Vinktar’s values filled in.
- Open replit.com/integrations, find MCP Servers for Replit Agent, and click + Add MCP server.
- Enter Vinktar as the Display name and paste the address below as the MCP Server URL. Leave Advanced settings alone: it holds custom headers, and the sign-in here is OAuth, not a header.
https://mcp.vinktar.com/mcp - Replit walks you through the OAuth flow. Your browser opens Vinktar: pick the workspace, the projects it may reach, and read, build or configure, then approve.
The consent screen grants one workspace, the projects the agent may reach, and read, build or configure. Setting Vinktar up needs configure, because the agent fetches the project’s write key and defines the events it adds. Reading analytics and errors needs only read.
2. Ask it to set Vinktar up
Set up Vinktar in this app: call get_install_guide on the Vinktar MCP server and follow it.It calls get_install_guide for the SDK and the layout, and get_project_keys for the write key. It defines each event it adds with define_event, then checks what arrived with get_setup_status. The guide says which environment variable to set. Put it where your app’s variables live.
The agent reads the tool list itself. Setting a project up is never counted against the monthly allowance. The questions after it are.
3. Check what arrived
Once events arrive, whats_changed is the overview, list_issues and get_issue are the errors with their stack traces, and get_setup_status reports an event that was defined but never sent. Ask it:
- What changed in this project since yesterday?
- Which errors hit the most people this week? Open the worst one and tell me where it breaks.
- Is anything in the tracking plan defined but never sent?
Every call lands on the project’s AI agents page as it is made.
What Replit’s docs say
One connection, all your projects
Replit’s docs say that once a server is connected, Agent fetches its tool list and makes it available across all your projects. The grant you approve names one Vinktar workspace, so if you build more than one product on Replit, leave the project unset at consent and the agent reaches every project in that workspace through list_projects.
Only servers you trust
Replit’s docs ask you to connect only to MCP servers you trust and to review the source before adding an unfamiliar endpoint. What Vinktar’s server can and cannot do with a workspace is written down on the security page. Security.
Checked
Replit’s documentation at https://docs.replit.com/build/connect-via-mcp was read on 2026-10-05, and the labels above are the ones it uses. A live run inside Replit’s agent has not been done yet. This page says what that documentation says a custom OAuth MCP server can do there, and what Vinktar’s server is; it does not say the two were tried together. When they have been, this line will say so.