Skip to main content
All MCP guides

MCP setup guide

Connect VS Code

Add Attorly as an MCP server in Visual Studio Code so GitHub Copilot's agent mode can use its tools for contracts, clauses and legal research.

Before you start

  • An Attorly Pro or Enterprise plan.
  • Visual Studio Code with GitHub Copilot and agent mode turned on.

Steps

  1. Create a key

    Create a key in Settings › Developers and choose VS Code. The settings page then shows the steps below with your key already filled in.

    Create a key for VS Code
  2. Add Attorly to VS Code

    Add Attorly as an MCP server in VS Code. Copilot's agent mode can then use its tools.

    Install it for your user from the terminal

    bash
    code --add-mcp '{"name":"attorly","type":"http","url":"https://attorly.ai/api/mcp","headers":{"Authorization":"Bearer lbmcp_your_api_key"}}'

    Or share it with your team in the workspace; VS Code asks each person for their own key

    .vscode/mcp.json
    {
      "inputs": [
        {
          "type": "promptString",
          "id": "attorly-api-key",
          "description": "Attorly API key",
          "password": true
        }
      ],
      "servers": {
        "attorly": {
          "type": "http",
          "url": "https://attorly.ai/api/mcp",
          "headers": {
            "Authorization": "Bearer ${input:attorly-api-key}"
          }
        }
      }
    }
  3. Check that it works

    Open the Copilot chat, switch to Agent and open the tools picker. Attorly's tools should be listed. Ask: “List my five most recent documents in Attorly.”

If it does not work

The server does not start.
Run MCP: List Servers from the command palette, select attorly and choose Show Output to see the error.
VS Code keeps asking for the key.
The workspace file asks once per person and stores the answer. Run MCP: List Servers, select attorly and restart it if you mistyped the key.
Something else went wrong.
Errors such as 401, insufficient_scope and rate_limited are explained in the MCP troubleshooting section. Every call also appears in Settings › Developers › Request logs, with the error it returned. MCP troubleshooting

Other clients