SmartSpectra MCP Server

Connect an AI assistant to your SmartSpectra account with the hosted MCP server — get or rotate your API key, register an iOS or Android app ID, download the OAuth config file, check plan usage and credits, and search these docs.

Important: SDK metrics are offered for general wellness and informational purposes only. SDK metrics have not been cleared by the FDA and may not be used for medical diagnosis or treatment.

Presage hosts a Model Context Protocol (MCP) server at:

https://mcp.presagetech.com/mcp

Connect it to an MCP-capable AI assistant — Claude Code, claude.ai, Codex, Cursor, or any other compliant client — and the assistant can manage your SmartSpectra developer account for you: fetch or rotate your API key, check your plan and credits, register apps, download the OAuth config file for a registered app, and search these docs.

It pairs with the AI agent skill: the skill teaches an assistant how to build with the SmartSpectra SDK; the MCP server gives it authorized access to your account, so "set up a new Android app and wire in my API key" works end to end.

What you need

A SmartSpectra account — the same login as the Developer Admin Portal. Sign-in happens in your browser through OAuth; the assistant never sees your password.
An MCP client that supports the streamable HTTP transport and OAuth. The server uses standard OAuth 2.1 with dynamic client registration, so no client ID or manual token setup is required — just the URL.

Connect from Claude Code

Add the server, then authenticate:

claude mcp add --transport http smartspectra https://mcp.presagetech.com/mcp

Run /mcp inside Claude Code, select smartspectra, and choose Authenticate. Your browser opens to the SmartSpectra login; approve the consent screen and the tools become available.

Connect from claude.ai or Claude Desktop

Open Settings → Connectors → Add custom connector.
Enter https://mcp.presagetech.com/mcp as the server URL and save.
Click Connect and complete the browser login.

Connect from Codex

Add the server, then authenticate:

codex mcp add smartspectra --url https://mcp.presagetech.com/mcp
codex mcp login smartspectra

codex mcp login opens your browser for the SmartSpectra sign-in. Run codex mcp list to confirm the server shows as connected.

Connect from other MCP clients

Any client that speaks streamable HTTP with OAuth works. For clients configured with JSON (Cursor and similar), add:

{
  "mcpServers": {
    "smartspectra": {
      "url": "https://mcp.presagetech.com/mcp"
    }
  }
}

The client discovers the OAuth endpoints automatically and opens a browser to sign you in.

Available tools

Tool	What it does
`api_keys.get`	Return your current SmartSpectra API key.
`api_keys.rotate`	Generate a new API key and invalidate the old one.
`usage.get_plan`	Report your plan tier, remaining credits, and next renewal date. Credits are counted per account, not per registered app.
`apps.list`	List your registered apps — platform, app ID, sandbox mode, and the registration ID used by the other app tools.
`apps.register`	Register (or update) an Apple or Android app ID, including sandbox mode and the descriptive fields the portal asks for.
`apps.get_config`	Fetch the OAuth config file for a registered app — `PresageService-Info.plist` on Apple, `presage_services.xml` on Android.
`apps.delete`	Delete an app registration, identified by the registration ID from `apps.list`.
`docs.map`	List the pages of this documentation site.
`docs.search`	Search this documentation.
`docs.read`	Read a documentation page: `/`, `/docs`, any `/docs/...` path, `/llms.txt`, or `/llms-full.txt`.

The server also exposes a using-smartspectra prompt that loads the agent skill content directly, for clients without skill support.

Setting up OAuth through an assistant

On iOS and Android, OAuth setup normally means registering your app in the portal by hand and downloading a config file. With this server connected, an assistant does both steps for you: apps.register with your bundle ID and Apple team ID (or package name and signing certificate SHA-256 fingerprint), then apps.get_config to fetch the config file and write it into your project at the right path.

iOS — Option 2: OAuth covers where PresageService-Info.plist goes and how to confirm OAuth is wired correctly.
Android — Option 2: OAuth covers presage_services.xml and the signing-certificate fingerprint the registration needs.

Sandbox mode is part of the registration. On iOS, ask for it when you want to test locally from Xcode builds pushed to your phone; without sandbox, the registration allows App Store and TestFlight builds only.

Confirmations for destructive actions

Tools that change your account — api_keys.rotate, apps.register, and apps.delete — never act on the first call. The first call returns a confirmation_required response describing exactly what will happen, plus a confirmation token; the assistant must call the tool again with that token to proceed. A token lasts five minutes, works once, and is bound to the exact arguments it was issued for, so a stale or altered confirmation cannot be replayed. Assistants surface this as an explicit "confirm this action" step — if yours does not, decline and run the action from the Developer Admin Portal instead.

Important: api_keys.rotate invalidates the current key immediately — every app using it stops authenticating until you deploy the new key.

Deleting your account is not available through the MCP server. Use the Developer Admin Portal.

Security notes

api_keys.get places your API key in the assistant's conversation context. Treat that conversation as sensitive, and rotate the key if you believe it leaked.
To revoke the assistant's access, remove or disconnect the server in your MCP client's settings. Sessions also expire on their own and require re-authenticating.