# Porticol with Cursor

> Connect Cursor to Porticol's MCP server, so its agent can search, read, send and run your API collections.

Canonical: https://porticol.app/integrations/cursor

Cursor reads MCP servers from one JSON file in your home folder. Add Porticol once and every workspace in Cursor on that computer gets it.

## Add the server to Cursor

```
{
  "mcpServers": {
    "porticol": {
      "type": "stdio",
      "command": "porticol-cli",
      "args": ["mcp"]
    }
  }
}
```

On Windows the file is `%USERPROFILE%\.cursor\mcp.json`. Save it, then reload MCP or restart Cursor. To allow writes, add `"--write"` to the args list.

## What it can do

- Search collections, requests and history for a query.
- Read a collection with its requests and examples, or one request of it.
- List the environments, or read one by id.
- Send a request and return what came back.
- Run a collection and wait for the finished run.
- Read recent sends and their results.
- Preview an OpenAPI document as a collection, without importing it.
- Create or change requests only when the server starts with --write.
- Secret values stay in Porticol: every result is masked, and a protected environment waits for a person in the app.

## Try it

Ask the agent to list your environments, pick staging, and run the checkout collection.

## Questions

**Where does Cursor keep MCP servers?**

In ~/.cursor/mcp.json on macOS and Linux, and %USERPROFILE%\\.cursor\\mcp.json on Windows. Cursor reads it when it starts or when you reload MCP.

**Does the file apply to every Cursor workspace?**

Yes. The file lives in your home folder, so each workspace on that computer reads the same server list.

## Try it on your own APIs

Free for one seat, on macOS, Windows and Linux.