Klint runs as a remote MCP server. Any client that can connect to a remote MCP server over HTTP can use it. For step-by-step setup in a specific agent, see Agent Setup.
Connection
| Server URL | https://mcp.tryklint.ai/mcp |
| Transport | HTTP (streamable) |
| Sign-in | OAuth, the standard MCP sign-in |
Use the exact URL, including /mcp. It’s an address for your MCP client, not a
page to open in a browser.
Add the URL and nothing else. A client that supports MCP sign-in opens the
Klint sign-in page the first time it connects. A request without a valid
sign-in gets 401.
Let your agent connect it
Paste this into the agent you want to connect. It reads For Agents and adds the server to its own configuration:
Read https://tryklint.ai/docs/for-agents/index.md and follow it to set yourself up to use Klint.Tools
| To | Call | With |
|---|---|---|
| Ask a new question | klint_start_agent |
prompt. Returns an agent_id. |
| Check whether Klint is done | klint_get_agent_status |
agent_id |
| Read the answer | klint_get_agent_reply |
agent_id |
| Ask a follow-up | klint_message_agent |
agent_id and message |
Put the whole task in one request: the goal, and requirements such as the platforms, audience size, location or time window.
Send a follow-up, such as “only accounts under 50K followers”, once the last
request is complete. Klint keeps what it found earlier, so a follow-up is
usually faster than a new request. Use klint_start_agent for an unrelated
question.
How a run goes
Klint reads real posts and accounts, so a request takes minutes: often 3 to 10, and longer for large requests. Start it, check its status about once a minute, and read the reply when Klint is done. Don’t start a new run for the same question; the first one is still working.
A run stops searching after 10 minutes and answers with what it has found by then.
Runs started over MCP are autonomous. Klint doesn’t ask questions back: it makes reasonable assumptions and states them in the answer.
The answer is Markdown, with a link to every account and post it cites.
Test the connection
Start a new conversation and ask:
Use Klint to look up the TikTok account @openai and give its follower count. Tell me which Klint tool you called.A working connection shows a call to klint_start_agent. Some clients put the
server’s name in front of the tool’s name.
Troubleshooting
| Symptom | Fix |
|---|---|
| No Klint tools appear | Check that the URL ends in /mcp. Restart the client, or start a new session, after saving its configuration. If the client asks, turn the server on for the conversation. |
401, or sign-in keeps repeating |
Remove the client’s saved sign-in for Klint, connect again, and finish signing in in the browser. |
| The agent answers without calling Klint | Name Klint in the question and ask the agent to say which tool it called. Check that the client isn’t waiting for you to approve the tool call. |
| No answer after several minutes | A run can take up to 10 minutes. Keep checking klint_get_agent_status rather than starting again. |
| “Klint is still working” | A follow-up was sent before the last request finished. Check the status, then send it again. |
| “No Klint agent has this ID” | Check the agent_id, or start a new run with klint_start_agent. |