Official Infisical MCP Server
Most browser automation work still happens through a UI a human drives. Infisical MCP server moves it into the conversation instead. Official Infisical MCP Server.
The Infisical Model Context Protocol server allows you to integrate with Infisical APIs through function calling. This protocol supports various tools to interact with Infisical.
The server publishes 11 tools. What each one is for:
create-secret — Create a new secretdelete-secret — Delete a secretupdate-secret — Update a secretlist-secrets — Lists all secretsget-secret — Get a single secretcreate-project — Create a new projectcreate-environment — Create a new environmentcreate-folder — Create a new folderinvite-members-to-project — Invite one or more members to a projectlist-projects — List all projectsInstructions — 1. Set the environment variables as described in the Environment Variables step. 2. Run the command to start the MCPConfiguration is passed through the environment: INFISICAL_HOST_URL, INFISICAL_UNIVERSAL_AUTH_CLIENT_ID, INFISICAL_UNIVERSAL_AUTH_CLIENT_SECRET, INFISICAL_AUTH_METHOD, INFISICAL_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
@infisical/mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Infisical's toolset — create-secret, delete-secret, update-secret and 8 more — is a fair guide to whether it matches your workflow. It is maintained by Infisical; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| create-secret | Create a new secret |
| delete-secret | Delete a secret |
| update-secret | Update a secret |
| list-secrets | Lists all secrets |
| get-secret | Get a single secret |
| create-project | Create a new project |
| create-environment | Create a new environment |
| create-folder | Create a new folder |
| invite-members-to-project | Invite one or more members to a project |
| list-projects | List all projects |
| Instructions | 1. Set the environment variables as described in the [Environment Variables ](#environment-variables) step. 2. Run the command to start the MCP Inspector. 3. Open the MCP Inspector UI in your browser and click Connect to |
#### Access Token
```json
{
"mcpServers": {
"infisical": {
"command": "npx",
"args": ["-y", "@infisical/mcp"],
"env": {
"INFISICAL_HOST_URL": "https://<custom-host-url>.com",
"INFISICAL_AUTH_METHOD": "access-token",
"INFISICAL_TOKEN": "<your-access-token>"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| INFISICAL_HOST_URL | Endpoint or connection string the server talks to. | Yes |
| INFISICAL_UNIVERSAL_AUTH_CLIENT_ID | Configuration value read at startup. | Optional |
| INFISICAL_UNIVERSAL_AUTH_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| INFISICAL_AUTH_METHOD | Configuration value read at startup. | Optional |
| INFISICAL_TOKEN | Credential the server authenticates with. | Yes |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.