
Prerequisites
- The Admin role in your Agent Vault project, to add, edit, and delete services, and to add them to access bundles
Service types
You choose a service’s type when you pick its template:HTTP APIs
Web APIs that the agent calls directly, such as GitHub, Slack, and Anthropic.
MCP servers
Remote MCP servers whose tools the agent calls, such as Linear and Notion.
Databases and SSH
PostgreSQL databases, MySQL databases, and SSH servers that the agent reaches with psql, mysql, or ssh.
Add a service
1
In your Agent Vault project, go to Services and select Add Service.
2
On the Choose a template panel, pick a template. The page for each service type describes its steps and fields, and Hooks describes the Hook step.
3
On the Review step, select Add Service. The service appears in the list, and agents can use it once you add it to an access bundle.
accessBundleIds.
Add a service to an access bundle
1
In your Agent Vault project, go to Access Bundles, select the access bundle, then select Add Service.
2
In the Services list, pick one or more services from the project. To create a service instead, select Create New Service and follow the steps for its service type. Infisical adds the new service to the access bundle when you save it.

3
If you picked existing services, select Add Service, or Add 2 Services if you picked two. Sessions on the access bundle can use the services within one poll interval.
Edit a service
To edit a service, go to Services, open the service’s actions menu, and select Edit. A change to a service applies in every access bundle that holds it. To let your own server allow or refuse the agent’s requests or connections to the service, add a hook on the Hook step.Remove or delete a service
Open the service’s actions menu and select one of these:- Remove From Bundle, on an access bundle’s page, takes the service out of that access bundle only (the service stays in the project)
- Delete, on the Services page, deletes the service from the project and from every access bundle that holds it
Service names
Each service’s name is unique in its project. Before services belonged to the project, two access bundles could each hold a service with the same name. When Infisical upgraded existing projects, the older of the two services kept its name, and Infisical renamed the other to<name>-<access bundle name>, such as github-on-call.
The agent connects to a database or SSH service by its name, so if Infisical renamed one, update the name in your agents’ infisical agent-vault connect commands.