# Claude Code

> Add the workspace as an HTTP MCP server with one command, then authenticate from inside Claude Code.

Source: https://docs.generalinput.com/mcp/clients/claude-code



If you use Claude Code on your own machine, the [`geni` CLI](/cli) is usually the better fit: it runs commands locally with your credentials and needs no connector. Reach for MCP when you want the platform's sandbox and full toolset instead of local execution, or when the work should live in the workspace's persistent `work/` directory.

## Steps [#steps]

Replace the URL with the one from the dashboard's MCP page.

```sh
claude mcp add --transport http general-input https://cloud.generalinput.com/v1/mcp/<organizationId>
```

Then, inside a Claude Code session, run `/mcp`, pick **general-input**, and complete the sign-in in the browser that opens. The token is stored by Claude Code and reused across sessions.

## Scope of the config [#scope-of-the-config]

`claude mcp add` writes to the local scope by default (this project, this user). Add `--scope user` to make the server available in every project, or `--scope project` to share it through the repository's `.mcp.json`.

## Notes [#notes]

* Tool permissions follow Claude Code's normal allow rules. Allow the server's tools once to stop per-call prompts.
* The `geni` skill and the MCP connector can coexist; the skill tells the model when to prefer local execution.