# MCP setup: Claude, ChatGPT, Claude Code and Cursor

Use `https://mcp.agentdzialek.pl/mcp`, the Streamable HTTP MCP endpoint. The ask SSE stream at `/v1/ask` is a separate interface, not an MCP server URL.

MCP uses the same metering as REST. An agent conversation can execute multiple charged tools; establish cost approval before starting. Six tools are exposed:

| Tool | REST | Credits |
| --- | --- | --- |
| check | GET /v1/check | 1 |
| parcel | GET /v1/parcel | 1 |
| layer | GET /v1/layer/{layer} | 1 |
| resolve | GET /v1/resolve | 1 |
| search | GET /v1/search | 1 |
| events | GET /v1/events | 1 |


## Claude web and Desktop

Add a custom remote connector in connector settings, name it landfeed and enter the `/mcp` URL. Select OAuth and automatic client registration when offered. This server supports dynamic registration; do not assume support for newer published-client-identity mechanisms. Finish landfeed consent with your account API key, enable the connector in a conversation and inspect its tools.

Claude Desktop can use the same account-level remote connector without a local stdio process. Organization policy can require an owner/admin to add it. UI labels depend on client version. [Official Claude instructions](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp).

## ChatGPT web

Open the plugins directory, add a custom MCP server, enter landfeed and the `/mcp` server URL, then select OAuth. Create the plugin, install it and select it in a conversation using `@`. Workspace permissions and restrictions determine access. If configuration is unavailable, check those permissions first. A custom API key is not a substitute for OAuth in this ChatGPT flow. [Official OpenAI instructions](https://developers.openai.com/api/docs/guides/custom-mcp-server).

## Claude Code

With Claude Code installed, run this terminal command, then open `/mcp` in Claude Code and complete browser authentication.

<!-- example:claude-code.sh -->
```sh
claude mcp add --transport http landfeed https://mcp.agentdzialek.pl/mcp
```


The example test captures CLI arguments without modifying a developer's client configuration. [Official Claude Code instructions](https://code.claude.com/docs/en/mcp).

## Cursor

Put this configuration in project `.cursor/mcp.json` or user `~/.cursor/mcp.json`. Enable landfeed in MCP settings and finish OAuth. Do not commit a credential.

<!-- example:cursor.json -->
```json
{
  "mcpServers": {
    "landfeed": {
      "url": "https://mcp.agentdzialek.pl/mcp"
    }
  }
}
```


[Official Cursor instructions](https://cursor.com/docs/mcp). The server must permit the exact client callback. `invalid_redirect_uri` requires the server operator to review that policy.

## Acceptance and troubleshooting

List the six tools after connecting, then ask for one named parcel layer and its source. Check that source, date and coverage survive into the answer. A tool list alone does not prove a successful paid call. Protocol tests are local evidence; each hosted client's actual consent and tool call need separate acceptance. Server OAuth support alone does not certify a connected client.

Client instructions checked on 2026-10-21. See [authentication](authentication.md) for tokens and consent failures.
