# Set up Known

You're reading this because someone wants you connected to Known, their company's shared memory: wikis and records that their team and its agents read and write together.

There are two ways in. If you can run shell commands, install the CLI. If you can't, or the person asks for it, connect through MCP. Sign-in happens in the person's browser either way, so there's no API key to ask for.

## Say little

The person asked for Known to be set up, not for a walkthrough. Do the work and keep what you tell them short.

- Don't repeat or summarize this page, explain what Known or MCP is, or list the steps you're about to take.
- Don't show a command's output unless the command failed.
- Speak when the person has to do something (signing in), and once at the end.
- At the end, say in one or two lines which organization and account you're connected as, and that it works. Don't list next steps or offer a tour unless they ask.

## In a terminal: install the CLI

If you can run shell commands on the person's machine (Claude Code, Codex, Cursor's agent, or any other terminal agent), use the `known` CLI. You run every command; the person only signs in.

1. Check whether it's already set up:

   ```
   known sessions
   ```

   If the command exists and lists a session, skip to step 4.

2. Install it. It needs Node 18 or later.

   ```
   npm install -g @future-unknown/known
   ```

   If the install is refused for permissions, don't use `sudo`: give the person the command to run themselves.

3. Sign in. First tell the person, in one line, that a browser window is about to open where they sign in to Known and choose their organization. Then run:

   ```
   known login
   ```

   The command waits up to five minutes for them and ends on its own, so allow it that long. If no browser opens, it prints the address to visit: give the person that.

4. Confirm it works. `known sessions` names the organization; then:

   ```
   known <org> ping
   ```

From here, `known <org> wiki wikis` lists the wikis you can read and `known <org> wiki` lists what you can do with them. The CLI guide: https://known.info/docs/cli.md

That is all a terminal agent needs. Add the MCP connection below as well only if the person asks for it.

## Connect through MCP

Use this when you can't run shell commands, or when the person asks for Known among your client's own tools. Known's MCP (Model Context Protocol) server address is:

```
https://api.known.info/mcp
```

Find your tool below and follow its steps. Change your own configuration where you can; the sign-in step always needs the person.

### Claude Code

1. Run:

   ```
   claude mcp add --transport http --scope user known https://api.known.info/mcp
   ```

2. Tell the person to restart Claude Code, run `/mcp`, select **known**, then **Authenticate**.
3. Known opens in their browser. They sign in, choose the organizations you may use, and select **Allow**.

Details: https://known.info/docs/connect-agent/claude-code.md

### Codex

1. Run:

   ```
   codex mcp add known --url https://api.known.info/mcp
   codex mcp login known
   ```

2. Known opens in the person's browser. They sign in, choose the organizations you may use, and select **Allow**.

Details: https://known.info/docs/connect-agent/codex.md

### Cursor

1. Add Known to `~/.cursor/mcp.json` (create the file if it doesn't exist; keep any servers already there):

   ```json
   {
     "mcpServers": {
       "known": { "url": "https://api.known.info/mcp" }
     }
   }
   ```

2. Tell the person to open **Cursor Settings → Tools & Integrations** and select **Connect** next to Known, then sign in and select **Allow** in the browser.

Details: https://known.info/docs/connect-agent/cursor.md

### VS Code (GitHub Copilot)

1. Add Known to `.vscode/mcp.json` in the project (keep any servers already there):

   ```json
   {
     "servers": {
       "known": { "type": "http", "url": "https://api.known.info/mcp" }
     }
   }
   ```

2. Tell the person to select **Start** above the `known` entry, then sign in and select **Allow** in the browser.

Details: https://known.info/docs/connect-agent/vs-code.md

### Claude (claude.ai, Claude Desktop)

You can't add a connector yourself. Give the person these steps:

1. Open **Customize → Connectors**, select **+ Add**, then **Add custom connector**.
2. Name it `Known` and paste `https://api.known.info/mcp`.
3. Select **Add**, then **Connect**, and sign in to Known in the browser.

Details: https://known.info/docs/connect-agent/claude.md

### ChatGPT

You can't add an app yourself. Give the person these steps:

1. Open **Settings → Apps → Advanced settings** and turn on **Developer mode**.
2. In **Apps**, select **Create**. Name it `Known`, paste `https://api.known.info/mcp`, and choose **OAuth**.
3. Select **Create**, then sign in to Known in the browser and start a new chat.

Details: https://known.info/docs/connect-agent/chatgpt.md

### Any other MCP client

Add `https://api.known.info/mcp` as a remote MCP server with browser (OAuth) sign-in. If you can't change your own configuration, tell the person how to add it in your settings.

## No Known account yet?

The person signs up at https://known.info with **Start free**. Their organization starts with a wiki called `general`.

## Check the connection

Once the person has signed in over MCP, list the wikis you can see in Known. Don't read them out: tell the person which organization you're connected to, in one line.

## Tell Known what got in the way

When a Known tool fails, is missing, or its words mislead you, send a note with `feedback_send` (from the CLI, `known <org> feedback`): one note per problem, saying what you were doing, what Known did, and what would have helped. Never include the organization's content. Known's team reads every note.

More: https://known.info/docs/connect-agent.md · All docs for agents: https://known.info/llms.txt
