MCP Server
Connect Claude, ChatGPT, Cursor, and any other MCP client to your Raster libraries over the Model Context Protocol.
The Raster MCP server is a remote
Model Context Protocol endpoint that lets
any MCP-capable client — Claude, ChatGPT, Cursor, VS Code, and others —
browse, upload, organize, and delete assets in your libraries, without writing
any client-side glue. It accepts two credentials: OAuth — recommended for
human-driven clients, where you sign in and pick one organization the
connection may access — or an organization API key sent as a
Authorization: Bearer token, the same keys used by the REST and
GraphQL APIs.
The endpoint
There is a single remote endpoint:
https://mcp.raster.app/| Detail | Value |
|---|---|
| Transport | Streamable HTTP (JSON-RPC over POST) |
| Auth | OAuth, or Authorization: Bearer <API_KEY> |
Every request must be authenticated. Missing or malformed credentials are
rejected with 401. See Authentication for how to
sign in with OAuth or create and scope an API key.
Agents with no Raster account start at the no-account endpoint
https://mcp.raster.app/anonymous, which mints an organization and key over
create_organization. See
Authentication.
Connect Raster
Connect Raster to your MCP client over OAuth. Pick your client below for a connect button or short setup steps, then a Raster sign-in where you choose one organization the connection may access:
Add a remote MCP server with this URL:
https://mcp.raster.app/Claude Desktop: Settings → Connectors → Add custom connector, then paste the URL.
Claude Code: Run claude mcp add --transport http raster with the URL.
Then approve the Raster sign-in and pick one organization.
Opens Cursor and a Raster sign-in — pick one organization at consent.
If Cursor doesn’t open, add the server to it manually with this URL:
https://mcp.raster.app/Opens VS Code and a Raster sign-in — pick one organization at consent.
If VS Code doesn’t open, add the server to it manually with this URL:
https://mcp.raster.app/Add a remote MCP server with this URL:
https://mcp.raster.app/- Run
codex mcp add raster --url https://mcp.raster.app/, or add it to~/.codex/config.tomlas a streamable-HTTP server. - Run
codex mcp login raster, approve the Raster sign-in in your browser, then pick one organization.
Add a remote MCP server with this URL:
https://mcp.raster.app/- In Antigravity, open Manage MCP Servers and add a custom server with the URL.
- Then Settings → Customizations → Installed MCP Servers → Authenticate, and approve in the browser.
Add a remote MCP server with this URL:
https://mcp.raster.app/- In v0, open settings and add an MCP server.
- Use the URL, then approve the Raster sign-in and pick one organization.
The client runs the MCP initialize handshake automatically and Raster's
tools appear in its tool palette. Manage and revoke every
connection under Settings → Connected apps. For the OAuth flow, scopes, and
discovery endpoints, see
Authentication.
Or have your agent add it — paste this prompt:
Add the Raster MCP server to this client: a remote Streamable HTTP server named "raster" at https://mcp.raster.app/ over OAuth. Then walk me through the OAuth sign-in for this client (reload it if needed, approve in the browser) and confirm its tools load.
Server-to-server with an API key
For automation, point any client at https://mcp.raster.app/ over the
Streamable HTTP transport with a Bearer Authorization header carrying an
organization API key — the same keys, with the same per-library access, you'd
use for the REST or GraphQL APIs. See
Authentication to create one.
{
"mcpServers": {
"raster": {
"url": "https://mcp.raster.app/",
"headers": { "Authorization": "Bearer YOUR_API_KEY" }
}
}
}Tools at a glance
Raster's tools cover the same surface as the REST and GraphQL APIs, plus a no-account create flow agents use to spin up a library and start uploading on a user's behalf. Full parameters and examples are on the Tools page.
| Tool | Access | Purpose |
|---|---|---|
whoami | Read | Resolve your key's organization + library scope. |
create_organization | Anonymous | Create an organization + library + API key for an agent — no account needed. |
create_library | Write | Create a library in an organization you have a key for. |
rename_library | Write | Rename a library. |
list_libraries | Read | List libraries in an organization. |
list_assets | Read | List assets in a library (paginated, tag filter). |
get_asset | Read | Get one asset by id. |
search_assets | Read | Search assets across libraries (ranked, highlights). |
list_tags | Read | List a library's tags, by usage count. |
upload_asset | Write | Upload one file from a URL or inline base64. |
upload_assets | Write | Upload up to 20 files in one call. |
delete_assets | Write | Move up to 100 assets to trash (soft delete). |
tag_assets | Write | Apply up to 20 tags to up to 100 assets. |
untag_assets | Write | Remove up to 20 tags from up to 100 assets. |
update_asset_description | Write | Replace one asset's description (verbatim). |
transfer_assets | Write | Move up to 100 assets between libraries. |
Where to go next
Authentication
Sign in with OAuth, or create and scope an API key, then authenticate the connection.
Tools
Every tool, its arguments, and a runnable example.
Resources
The read-only raster:// resource URIs.
Errors
The tool-error envelope and the shared error-code reference.
Need help?
Reach out at support@raster.app, or browse the REST and GraphQL references — the same API keys and payload shapes apply, so most questions transfer.