---
title: "For Agents"
description: "How an AI agent sets itself up to use Klint. It adds the MCP server, hands sign-in to the person, checks that it works and reports back."
---

> Documentation Index
> Fetch the complete documentation index at: https://tryklint.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# For Agents

If you're setting up an agent, paste this into it:

```text
Read https://tryklint.ai/docs/for-agents/index.md and follow it to set yourself up to use Klint.
```

The rest of this page is written for the agent. To set Klint up yourself, follow
the guide for your agent in [Agent Setup](https://tryklint.ai/docs/agent-setup/).

## Instructions for the agent

These are Klint's official setup instructions, published at
`https://tryklint.ai/docs/for-agents/index.md`. Follow them from Step 1.

Klint researches social media: creators, brands, posts, trends and communities
on TikTok, Instagram, YouTube, X and Reddit. You use it through its MCP server.
You will add the server to your own configuration, hand sign-in to the person,
check that it works, and report back.

Follow these rules throughout:

- Run the commands and edit the files yourself. Finishing sign-in in the browser,
  and restarting the client when it needs it, are the only steps the person
  does.
- Add Klint for the current project unless the person asks for every project.
  Ask before changing a file that applies to every project.
- Never ask the person to paste a password, token or key into the chat. Sign-in
  happens in their browser.
- If you can't do a step, give the person the exact step to take and say that it
  isn't done.
- If your client can't connect to a remote HTTP server with OAuth sign-in, stop
  and tell the person. Klint has no other way to connect, and you never need a
  key.

## Step 1: Check whether Klint is already set up

If you already have tools whose names end in `klint_start_agent`,
`klint_get_agent_status`, `klint_get_agent_reply` and `klint_message_agent`,
Klint is set up: go to [Step 4](#step-4-check-that-it-works). Clients often add
a prefix to each tool's name, such as `mcp__klint__`.

If your configuration already has a server named `klint` but its tools aren't
available, don't add it again or remove it: go to
[Step 3](#step-3-restart-and-sign-in).

## Step 2: Add the server

1. Fetch `https://tryklint.ai/docs/agent-setup/llms.txt`. It lists a setup guide
   for each of 34 agents, with a link to each guide's Markdown.
2. Fetch the guide for your client, using its link from that list, and follow
   its steps to add the server and sign in. Signing in is the person's step: tell them
   what to do when you reach it.
3. If the guide offers a choice between the current project and every project,
   use the current project. If its only option applies to every project, such
   as Codex's `~/.codex/config.toml`, ask the person first. If they say no,
   don't add it: give them the step in case they want to do it themselves, and
   report that Klint wasn't added.

If your client has no guide, add a remote MCP server with these settings:

| | |
| --- | --- |
| Name | `klint` |
| URL | `https://mcp.tryklint.ai/mcp` |
| Transport | HTTP (streamable) |
| Auth | OAuth, the standard MCP sign-in |

Add the URL only, with no `Authorization` header. Your client opens Klint's
sign-in page the first time it connects.

## Step 3: Restart and sign in

Most clients load a new MCP server only after a restart or in a new session,
and you can't use Klint until the person has also signed in. If the Klint tools
are already available to you, go to [Step 4](#step-4-check-that-it-works).

If they aren't, don't test. The person has to restart the client and sign in,
and the restart ends this session, so report first: go to
[Step 5](#step-5-report-back), report the setup as added but not verified, and
give the person this line to paste into the new session:

```text
Continue Klint setup from Step 4 of https://tryklint.ai/docs/for-agents/index.md.
```

## Step 4: Check that it works

1. Check that the four Klint tools from [Step 1](#step-1-check-whether-klint-is-already-set-up)
   are available. This costs nothing. If they aren't, the person usually still
   needs to sign in: report the setup as waiting on sign-in, with your client's
   sign-in step.
2. Ask the person before you run a test, because each run uses their Klint
   credits. If they agree, call `klint_start_agent` with this small request:

   ```text
   Look up the TikTok account @openai and give its follower count.
   ```

   The connection works if `klint_start_agent` returns an `agent_id`. You don't
   need to wait for the answer. An answer you write yourself doesn't count.

## Step 5: Report back

Tell the person, in this format:

```text
Klint setup
- Added: <the file you changed | the command you ran | already set up | not added>
- Verified: <yes, a test run started | tools available, test skipped | not yet, waiting on a restart | not yet, waiting on sign-in | no, not added>
- Your next steps: <each step the person takes, in order, or "nothing">
```

The person's next steps can include, in this order:

- Restart the client, by name: for example, "Restart Codex".
- Sign in to Klint, with the sign-in step from your client's guide. Leave this
  out if they already signed in.
- Paste the continue line from [Step 3](#step-3-restart-and-sign-in) into the
  new session. Include the line itself after the summary.
- Run the command you gave them, if they chose to add Klint themselves.
- Use a client that can connect to a remote MCP server with OAuth sign-in, if
  theirs can't.

Once Klint is connected, its tools explain how to use them. For the tools, how
a run works and troubleshooting, read
`https://tryklint.ai/docs/agent-setup/any-mcp-client/index.md`.

Source: https://tryklint.ai/docs/for-agents/index.mdx
