Skip to main content

Gearset Agent MCP integrations

Written by Mateusz Kochanowicz

You can give Cam access to a number of MCP servers so it can connect to your external systems. Team Owners can add servers; Team Members will connect using their own OAuth connections.

Gearset supports the following MCP integrations:

Managing connections

Some connections require you to perform some steps before you can connect in Gearset.

Allow Gearset to access Atlassian Rovo MCP

Adding a connection for the team

As a Team Owner, navigate to the agent's Settings page. Clicking Add will allow you and your team to connect that integration.

Connecting to an integration

Once the connection has been added, you will be able to click Connect.

You will then be taken to the OAuth sign in flow for that connection, where you will be able to configure any permissions that connection supports.

Using MCP connections

Example uses

MCP servers allow the agent to query data and take actions in your external services. There are a number of ways this can be valuable to help the agent gather extra context for more accurate responses or update data as it works.

  • Using the Atlassian Rovo MCP the agent can explore Confluence docs where additional requirements or best practices live.

  • Using Linear the agent could search old tickets where implementation decisions were decided to guide future work.

  • The agent could update Confluence docs as it works, or submit research findings so others can find them later.

Handling Agent requests

Certain actions from MCP servers will require human approval. The approval prompt will appear in the chat at which point you can either approve or deny.

Did this answer your question?