---
title: AI coding agents | API Docs
description: Install the Linq plugin so Claude Code, Cursor, or Codex can build on Linq for you.
---

The [Linq plugin](https://github.com/linq-team/linq-ai) teaches your coding agent how Linq works: conventions it should follow, guided walkthroughs, and direct access to the API through [MCP](https://modelcontextprotocol.io). Install it once and you can ask for what you want in plain language instead of pasting docs into a prompt.

It ships two skills — one for setting up a brand-new account, one for building on an account you already have — and an MCP server with two tools:

| Tool          | What it does                                                 |
| ------------- | ------------------------------------------------------------ |
| `search_docs` | Looks up the exact method and parameters before writing code |
| `execute`     | Runs TypeScript against your authenticated account           |

## 1. Authenticate the CLI

Both the CLI and the plugin’s MCP server read the same credential, so this one step covers everything.

Terminal window

```
npm install -g @linqapp/cli@latest
linq login --token <your-api-token>
```

This writes `~/.linq/config.json`. The MCP server falls back to that file when `LINQ_API_V3_API_KEY` is not set — which matters on macOS, where an editor launched from the Dock never sees environment variables from your shell profile.

Note

Prefer `linq login` over exporting a variable. It authenticates the CLI and the plugin together, for every project on the machine.

## 2. Install the plugin

- [Claude Code](#tab-panel-4)
- [Cursor](#tab-panel-5)
- [Codex](#tab-panel-6)

Run both commands inside Claude Code:

```
/plugin marketplace add linq-team/linq-ai
/plugin install linq@linq-ai
```

Then reload so the current session picks it up:

```
/reload-plugins
```

Confirm the MCP server attached:

Terminal window

```
claude mcp list
```

Expect `plugin:linq:linq … ✔ Connected`.

Caution

`claude plugin details linq` reports `MCP servers (0)` even when the server is working. Use `claude mcp list` to check.

Copy the plugin into your local plugins directory:

Terminal window

```
git clone https://github.com/linq-team/linq-ai
mkdir -p ~/.cursor/plugins/local
rsync -a --exclude .git --exclude node_modules linq-ai/ ~/.cursor/plugins/local/linq/
```

Then run **Developer: Reload Window**.

Once **Linq** is listed in the Cursor marketplace, you’ll be able to install it from the **Customize** page instead.

Caution

Copy the directory — do not symlink it. Cursor rejects a symlink whose target sits outside `~/.cursor/plugins/local`.

Point Codex at the repository as a plugin source. The manifest at `.codex-plugin/plugin.json` declares the same skills and MCP server.

## 3. Try it

Ask your agent in plain language. It picks the right skill on its own:

```
Add Linq messaging to this app — I already have an API key
```

```
What are my Linq phone numbers?
```

```
Write me an Express webhook handler for Linq
```

You can also invoke a skill directly:

- `linq-quickstart` — new account: install the CLI, sign up, provision a number, send a first iMessage with effects, reactions, and live webhooks
- `linq-build` — existing account: send from code, receive webhooks with signature verification, handle opt-outs and rate limits

execute sends real messages

The `execute` tool runs against your live account. Asking it to send a message delivers a real message to a real phone. The skills instruct the agent to confirm with you first, but treat it as production.

## Without the plugin

If you would rather not install anything, point your agent at [`llms-full.txt`](https://docs.linqapp.com/llms-full.txt) — the complete documentation in a single file. See [LLM-friendly docs](/guides/resources/faq#llm-friendly-docs/index.md).