Docs / MCP

MCP

MCP (the Model Context Protocol) is how AI assistants and agents call outside tools. Connect this server and your AI can read Pressure by itself: you ask, it calls the tools, the reading lands in the answer. The endpoint is https://api.pressureatlas.com/mcp, over streamable HTTP.

Connect a client

Every client below points at the same server, https://api.pressureatlas.com/mcp, and signs in with OAuth: a browser window opens the first time the server is used, registration is automatic, and there is no key to paste. Pick your client.

ChatGPT

On chatgpt.com, add the server as a connector:

  1. Turn on Developer mode under Settings, Security and login, Developer mode.
  2. Open Settings, Plugins, Browse plugins, then choose + at the top right.
  3. Name it, keep Server URL selected, and paste the server URL below. Leave Authentication on OAuth; the advanced settings fill themselves in.
  4. Tick I understand and want to continue, then Create.
  5. Sign in through the window that opens.
server url
https://api.pressureatlas.com/mcp

The ChatGPT desktop app takes an API key instead. Create an API key in the app, then open Settings, Plugins, Add, Add MCP server. Name it, pick Streamable HTTP, paste the server URL, and under Headers add x-api-key with your key.

For more information, see OpenAI's developer mode documentation.

Codex CLI

To use the server with the Codex CLI, add it to your ~/.codex/config.toml file. To learn more, see the OpenAI Codex MCP documentation.

~/.codex/config.toml
[mcp_servers.pressure-atlas]
url = "https://api.pressureatlas.com/mcp"

After you add the server, sign in with OAuth:

command line
$ codex mcp login pressure-atlas

To authenticate with an API key instead of OAuth, set bearer_token_env_var to the name of an environment variable that holds your key. In this example, PRESSURE_ATLAS_API_KEY is a placeholder; replace it with the actual name of your environment variable.

~/.codex/config.toml
[mcp_servers.pressure-atlas]
url = "https://api.pressureatlas.com/mcp"
bearer_token_env_var = "PRESSURE_ATLAS_API_KEY"

To check any connection, ask the client: "What is today's pressure?"

Manage connections

Every client you connect with OAuth appears as a connection on your usage page, with the date it connected and when it last called a tool. Choose Disconnect to revoke that client's access: its sign-in stops working, and a token it already holds lapses within the hour.

Disconnecting removes nothing else. To bring a client back, run the connect steps above again for that client - it signs in and asks for your approval, the same as the first time. API keys are separate: they are not connections, and you manage them on the keys page.

Tools

Every account sees the full catalog of tools. Data tools serve the most recent 5 closed days; a requested date window is acknowledged in the response and the same window is served.

ToolReturns
list_datasetsThe catalog and your access. Call this first.
get_latest_pressureThe newest closed day's reading, 0-5 with a label.
get_recent_pressureDaily readings for a window as compact CSV.
get_latest_metricThe newest closed day's reading of any other metric in the catalog, on that metric's own scale. Pass metric: the slug from list_datasets.
get_recent_metricDaily readings of any other metric for a window as compact CSV.
searchFree-text search over the catalog; returns ids for fetch.
fetchOne document by id, e.g. dataset:macro.
get_usageYour quota position today; costs no daily quota.
tools/call
{ "name": "get_latest_pressure",
  "arguments": { "dataset": "macro" } }
result
Pressure: 3.2 / 5 (building) on 2026-08-19
(Macro (Global)).