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

# MCP

## About the SDK MCP

The OneS1ght SDK MCP lets your coding agent look up the SDK docs for you, write the integration code, and analyze logs to fix errors.

## Example prompts

Try asking your coding agent things like:

* **Install the SDK** — "Add the OneS1ght SDK to this app. Positioning should start on the store map screen."
* **Explain an error code** — "Fix the E3003 that shows up in the logs."
* **Find a problem from symptoms** — "The app runs, but no coordinates are being uploaded."
* **Check integration status** — "Can you check how the SDK integration is doing right now?"
* **Upgrade the version** — "Upgrade the SDK to the latest version."
* **Check spaces** — "Tell me which buildings and floors this key can see."

## Notes

* The OneS1ght MCP supports the **iOS, Android and Flutter SDKs**.
* Tell your coding agent the target platform (iOS · Android · Flutter). For a Flutter app, say Flutter to get Dart snippets; error codes come with both the iOS and Android meanings.
* The MCP is **read-only**. It does not change console settings, zones or keys — do that in the [OneS1ght Console](https://console.ones1ght.com).
* Integration status checks only look at **recent logs** received with the connected SDK key (24 hours by default, up to 30 days).
* The MCP stops working if the registered API key is revoked or the service is suspended.

> [!TIP]
>
> **Recommendation** — Issue a separate **Development key** for the MCP connection. The key is stored as-is in your coding agent's config file, so
> do not commit it to a repository or share it with others. Always review code written by a coding agent before merging it.

## Connecting the MCP

Issue an API key from the **Mobile SDK** menu in the console ([Mobile SDK Key Management](/en/console/sdk-keys)), then replace `YOUR_SDK_API_KEY` in the examples
below with your key. The server URL and auth header are the same for every client.

### Connecting from Claude Code

1. Run the command below in a terminal.

```bash theme={null}
claude mcp add --transport http onesight https://console.ones1ght.com/api/sdk/v1/mcp --header "X-SDK-Key: YOUR_SDK_API_KEY"
```

2. Check that it is registered. If `onesight` appears in the list, you are connected.

```bash theme={null}
claude mcp list
```

### Connecting from Codex

1. Open `~/.codex/config.toml`. Create it if it does not exist.
2. Add the following and save.

```toml theme={null}
[mcp_servers.onesight]
url = "https://console.ones1ght.com/api/sdk/v1/mcp"

[mcp_servers.onesight.http_headers]
X-SDK-Key = "YOUR_SDK_API_KEY"
```

3. Restart Codex.

### Connecting from Cursor

1. Open `~/.cursor/mcp.json`. To use it only in this project, use `.cursor/mcp.json` in the project folder instead.
2. Add the following and save.

```json theme={null}
{
  "mcpServers": {
    "onesight": {
      "url": "https://console.ones1ght.com/api/sdk/v1/mcp",
      "headers": { "X-SDK-Key": "YOUR_SDK_API_KEY" }
    }
  }
}
```

3. Check that `onesight` is enabled in the **MCP** screen of Cursor settings.

### Connecting from other MCP clients

Any client that supports HTTP MCP can connect to the same URL. Put your key in the `X-SDK-Key` request header.

```text theme={null}
https://console.ones1ght.com/api/sdk/v1/mcp
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.