Connect with Visual Studio

Connect Visual Studio’s MCP support to the Aembit MCP Server to query audit logs and events directly from your IDE.

Prerequisites

Visual Studio 2022 or later with MCP support
Aembit API Token and MCP Service URL (see Connect to the MCP Server)

Configure the MCP connection

Create the configuration file.

In your project root (or user config directory), create a file named .mcp.json:
```
{
  "servers": {
    "aembit": {
      "url": "https://<tenantId>.mcp.useast2.aembit.io/mcp",
      "headers": {
        "Authorization": "Bearer <apiToken>"
      }
    }
  }
}
```
Replace:
- <tenantId> with your tenant identifier from the Aembit Admin UI
- <apiToken> with your API Token
Add .mcp.json to your .gitignore file to prevent committing it to version control.

(Optional) Scope to a resource set.

Add the X-Aembit-ResourceSet header to query a specific resource set:

{
  "servers": {
    "aembit": {
      "url": "https://<tenantId>.mcp.useast2.aembit.io/mcp",
      "headers": {
        "Authorization": "Bearer <apiToken>",
        "X-Aembit-ResourceSet": "<resourceSetId>"
      }
    }
  }
}

Restart Visual Studio to load the configuration.

Verify the connection

Visual Studio may prompt for permission when MCP tools are first invoked. Select Allow to enable Aembit queries.

Test the connection by asking about available tools or requesting recent audit logs.

Usage notes

Keep these points in mind when using Visual Studio’s MCP support with the Aembit MCP Server.

The MCP Server expects structured JSON commands, not free-form natural language.
The MCP Server only supports read operations; you can’t modify Aembit data through this connection.
Queries operate on your default resource set unless you specify X-Aembit-ResourceSet.

Next steps

See the Prompt Library for example prompts and best practices.
If you have connection issues, see Troubleshooting.

Learn more

Visual Studio MCP documentation