ADLANE ACCOUNT MCP SERVER · READ-ONLY · OAUTH

Adlane account MCP server.

Your Adlane workspace, in context. Give your AI assistant a small, read-only view of your Adlane account. Identify your profile and discover the workspaces available to you.

The hosted Adlane MCP server needs no API keys, no local process and no developer setup: paste one endpoint into your AI client, sign in with Adlane, and ask.

Connect your assistant

What you can do

Confirm your identity

Read the profile associated with the Adlane account you authorised.

Discover workspaces

List your available workspaces so you can identify the business you want to work with.

Choose the next connection

For campaign reporting, add the separate Google Ads or Meta Ads MCP connection.

SETUP GUIDE

From connection to first answer.

You need an MCP client with remote HTTP and OAuth support, plus a Adlane login with access to the data you want to read. Client availability can depend on your plan or administrator.

Add a remote MCP server
Open your AI client’s MCP or connector settings. Add a server named “Adlane Adlane account” and paste the URL below. Choose Streamable HTTP if your client asks for a transport.
https://mcp.adlane.app/mcp
Sign in and review consent
Start the connection in your client and follow the browser sign-in. Review the requested access, approve if appropriate, then return to your AI client.
Sign in to your Adlane account and review the MCP client consent. This connection exposes your profile and workspace list.
Check the tools
Refresh the connection if needed. You should see 2 tools, including get_profile. Ask your assistant to discover workspaces before requesting a report.
Ask your first question
Start with a specific scope. Copy or adapt this prompt:
Read my Adlane profile and list my available workspaces. Summarise which businesses are available. Do not infer campaign performance from workspace information.

Set up the Adlane account MCP server in Claude, Claude Code, Cursor or VS Code

Every client below supports remote HTTP MCP with OAuth. The server name is yours to choose; adlane-adlane is used in the examples.

Claude (web and desktop)

Open Settings, choose Connectors, then Add custom connector. Paste https://mcp.adlane.app/mcp as the remote MCP server URL and save. Click Connect on the new connector to start Adlane sign-in.

Claude Code

Run the command below in your terminal, then type /mcp inside Claude Code to authenticate.

claude mcp add --transport http adlane-adlane https://mcp.adlane.app/mcp

Cursor

Add this entry to .cursor/mcp.json in your project or to the global MCP settings. Cursor opens the browser for OAuth the first time the server is used.

{
  "mcpServers": {
    "adlane-adlane": {
      "url": "https://mcp.adlane.app/mcp"
    }
  }
}

VS Code (GitHub Copilot agent mode)

Create .vscode/mcp.json with this entry, then start the server from the MCP view.

{
  "servers": {
    "adlane-adlane": {
      "type": "http",
      "url": "https://mcp.adlane.app/mcp"
    }
  }
}

Desktop clients without remote OAuth support

If your client accepts an mcpServers JSON configuration but cannot connect to a remote OAuth server directly, the third-party mcp-remote bridge can make the connection. Install Node.js with npm first, merge this entry into your configuration, restart the client and complete browser sign-in. Native remote MCP support is preferable when your client provides it. Do not paste provider passwords or access tokens into any configuration.

{
  "mcpServers": {
    "adlane-adlane": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.adlane.app/mcp"
      ]
    }
  }
}

Available Adlane account MCP tools

These tools read data. They cannot create campaigns, change budgets, publish ads or approve Adlane proposals.

get_profilelist_workspaces

This server does not read campaign reports, edit workspaces, create campaigns or approve proposals. Advertising connections are separate and require their own provider sign-in.

Connection troubleshooting

No accounts or data?

This server does not read campaign reports, edit workspaces, create campaigns or approve proposals. Advertising connections are separate and require their own provider sign-in.

Sign-in did not finish?

Complete consent in the same browser session. If a desktop bridge uses a local return address, allow that callback in your browser. Reconnect from the client if the sign-in expires.

Access stopped working?

Reconnect after access is revoked or a provider token expires. For Meta, expired tokens require a new sign-in. Check your provider permissions before repeatedly retrying a failed report.