> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up Deepline MCP

> Authorize remote MCP access and verify tool discovery before provider execution.

[Human guide: work with your agent →](https://deepline.com/docs/human/mcp/setup.md)

Connect Deepline as a remote MCP server and verify authorization before running
a lookup. Your first task is tool discovery in the intended workspace.

## Before you start

Use an MCP client that supports remote servers and Deepline's authorization
flow. Shell-capable agents can instead use [CLI setup](https://deepline.com/docs/sdk-v2/coding-agents.md).

## 1. Add the remote server

Use your client's custom connector or remote-server setup. Supply:

| Field | Value |
| - | - |
| Name | `deepline` |
| Remote MCP server URL | `https://code.deepline.com/api/v2/mcp` |
| OAuth Client ID | Leave empty for the normal registration flow |
| OAuth Client Secret | Leave empty for the normal registration flow |

Complete Deepline sign-in and select the workspace the client should use.
Do not copy a provider API key into the OAuth fields.

Client screens vary. For Claude, consult its
[remote connector instructions](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp).
The remote server must be reachable from the client's execution infrastructure.

## 2. Test discovery before execution

Ask the client:

```text theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
Inspect the Deepline tools and resources available through this connection.
Confirm the selected workspace where available. Find the current contract for
work-email lookup. Do not execute provider requests or update external systems.
```

Read the returned identifier and required inputs. A plausible tool name is not
a valid payload. Search results do not establish authorization for every action.

> [!TIP]
>
> Deepline discovery works, the intended workspace is authorized, and the
> selected contract accepts the identifiers you plan to supply.

## 3. Run one bounded task after review

Use one known person or a small reviewed sample. Ask for source evidence,
validation outcomes, unresolved results, and actual Deepline usage.
Use [Work email](https://deepline.com/docs/plays/task-find-work-email.md) to choose the right input path.

MCP access does not change the Play's schema or create a universal fallback
route. The same workspace and action contracts still apply.

## If connection or authorization fails

Check the remote URL and completed authorization. Confirm the workspace rather
than repeatedly adding connectors. Distinguish network reachability from
provider access and no-result outcomes.

Ask your client to explain the specific failed boundary before retrying.
For recurring custom work, continue with [Write Plays](https://deepline.com/docs/sdk-v2/plays.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.