Set up Deepline MCP

1. Have your context ready

Your client must support a remote connector and Deepline sign-in. Connector creation and sign-in may require you to use the client settings.

2. Ask your agent

Paste this into your agent, then provide your task and example inputs when it asks:

/deepline-gtm Help me add Deepline as a remote MCP connection. Use https://code.deepline.com/api/v2/mcp as the server URL. For normal registration, leave the OAuth client ID and client secret empty. Walk me through the settings I must change myself and the Deepline sign-in. Then inspect the available tools and confirm the workspace where it is available. Discover a work-email workflow, but do not execute it.

Complete any requested sign-in yourself. Give the agent the missing information before approving execution. Provider-backed work can incur usage.

3. Review the result

The agent discovers Deepline through the connection. Required inputs are known before any lookup. Provider API keys do not belong in the connector’s OAuth client secret field. Ask your agent:

/deepline-gtm Compare the result with the acceptance rule we agreed. Show the evidence for accepted and rejected outcomes, unresolved questions, and recorded Deepline usage where work ran. If work is still running or a response is uncertain, inspect the original saved execution before proposing another request. Explain the next decision I need to make.

Approve a larger job, recurring work, or external changes only after reviewing that decision.

Check your understanding

Should a provider API key be entered as the MCP OAuth Client Secret?

Show the answer

No. The normal remote registration flow leaves that field empty. Provider connections belong to the Deepline workspace integration flow.

​1. Have your context ready

​2. Ask your agent

​3. Review the result

​Check your understanding

​Related guides

1. Have your context ready

2. Ask your agent

3. Review the result

Check your understanding

Related guides