Authorize remote MCP access and verify tool discovery before provider execution.
Human guide: work with your agent →Connect Deepline as a remote MCP server and verify authorization before running
a lookup. Your first task is tool discovery in the intended workspace.
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.
The remote server must be reachable from the client’s execution infrastructure.
Inspect the Deepline tools and resources available through this connection.Confirm the selected workspace where available. Find the current contract forwork-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.
Deepline discovery works, the intended workspace is authorized, and the
selected contract accepts the identifiers you plan to supply.
Use one known person or a small reviewed sample. Ask for source evidence,
validation outcomes, unresolved results, and actual Deepline usage.
Use Work email 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.
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.
