Connect your agent

Point your MCP client at this endpoint:

https://api.smry.ai/mcp

The server connects and lists its tools straight away. Anything that touches your account needs a credential — a browser approval, or a key.

Before you begin

A smry account — start free. The free plan connects.
A client that supports remote MCP servers — Claude Code, Claude Desktop, Codex, Cursor, VS Code, and most others do.

Add the server

Claude Code
Codex
Cursor
VS Code
Anything else

claude mcp add --transport http smry https://api.smry.ai/mcp

The parts of that command:

claude mcp add registers a server with Claude Code.
--transport http means smry is hosted at a URL. Nothing runs on your machine.
smry is a name you make up. It labels smry’s tools in Claude’s output. Calling it library would work identically.
https://api.smry.ai/mcp is where the server lives.

You should see Added HTTP MCP server smry with URL: … — that means the entry was saved, not that it connected yet.

export SMRY_API_KEY="smry_your_key"
codex mcp add smry \
  --url https://api.smry.ai/mcp \
  --bearer-token-env-var SMRY_API_KEY

Codex reads the key from your environment at startup, so it never lands in a config file. Create the key in the Developer console.

~/.cursor/mcp.json

{
  "mcpServers": {
    "smry": {
      "type": "http",
      "url": "https://api.smry.ai/mcp",
      "headers": { "Authorization": "Bearer ${env:SMRY_API_KEY}" }
    }
  }
}

Use ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one. Keep the key in your environment and out of the file.

.vscode/mcp.json

{
  "servers": {
    "smry": {
      "type": "http",
      "url": "https://api.smry.ai/mcp",
      "headers": { "Authorization": "Bearer ${input:smry-key}" }
    }
  },
  "inputs": [
    {
      "id": "smry-key",
      "type": "promptString",
      "description": "smry API key",
      "password": true
    }
  ]
}

VS Code asks for the key once and keeps it in the OS keychain. Start the server from the gutter action in mcp.json.

Server name: smry
Transport: Streamable HTTP
URL: https://api.smry.ai/mcp

Any client that speaks remote MCP works. Clients that cannot complete a browser sign-in can send a personal key instead:

Authorization: Bearer smry_your_key

Run claude mcp list. smry shows ✔ Connected with no credential at all, and all 28 tools are listed. Connecting and listing need no account.The tools that touch your library are different. The first one your agent calls fails with an authentication error until a credential arrives. Open a session, run /mcp, pick smry, and approve access in the browser. smry never asks an agent for a password — a person approves, once. The other tabs send a Bearer key instead and skip the browser entirely.

What you see	What it means	What to do
`✔ Connected`, tools listed	The server answered. It says nothing about your account.	Call an account tool and find out.
An account tool returns an authentication error	No credential has reached smry yet.	Run `/mcp` and approve, or send a key.
`✘ Failed to connect`	The client cannot reach the URL.	Check the URL, then your network.

Access renews in the background. You should not have to sign in again on a schedule.

Prove it works

Ask your agent something only smry can answer:

use the smry server to read https://www.nasa.gov/news-release/nasa-sets-coverage-for-agency-crew-mission/ and tell me the three main claims

You do not normally need to name the server — your agent picks tools on its own. Naming it here guarantees the answer came through smry rather than the agent’s own browsing.Then try one that needs your account:

what have i saved recently?

If an agent is doing this setup for you, it should run the command itself. You only need to sign in and approve access in the browser.

What your agent can do once connected

28 tools, but you will trigger a handful of them constantly:

Ask for this	Tool	What it saves you
”read this link and tell me X”	`search_article`	Returns the paragraphs that answer X, not the whole page
”save this so i can read it later”	`save_article`	The article, kept as clean text with the original
”what did i save about pricing?”	`list_library_objects`	One search across saved items, notes, and highlights
”what’s new in my feeds?”	`get_feed_changes`	Only what arrived since last time
”follow this creator”	`follow_feeds`	A feed URL, a site, an X account, or a TikTok profile
”watch this page for changes”	`create_monitor`	A page with no feed becomes one

The full list is in the MCP tool reference.

If it isn’t working

The tools are listed but calling one fails

Expected, until you sign in. Listing tools needs no credential; calling an account tool does. Run /mcp, pick smry, and approve in the browser, or add a Bearer key to the client config.

It still fails after adding a key

The key is mistyped, expired, or revoked. Create a fresh one in the Developer console and restart the client. A credential header always wins: once one is present, smry uses it rather than falling back to a browser sign-in, so a bad key never silently degrades to anonymous access.

Tools appear but the account looks empty

You are probably signed in as a different account than the one holding your library. Ask your agent what have i saved recently? — if it answers for an empty library, disconnect and approve again with the right account.

Nothing changed after editing the config

Restart the client. Most read MCP configuration only at startup.

Keep one credential per client

Give each client its own key. Then you can see which one made a change, and revoke one without interrupting the others.

Never deploy a shared bridge with one key serving many people. Each person must present their own credential, or their libraries merge.

Things to ask for first

Prompts worth pasting once your agent is connected.

What you can do

Read anything, keep it, follow it, ask about it later.

Get connected

Agent workflows

Recipes

Reference

Connect your agent

Before you begin

What your agent can do once connected

If it isn’t working

Keep one credential per client

Next

Things to ask for first

What you can do

​Before you begin

​What your agent can do once connected

​If it isn’t working

​Keep one credential per client

​Next

Things to ask for first

What you can do

Before you begin

What your agent can do once connected

If it isn’t working

Keep one credential per client

Next