Skip to main content

​
Overview

Integrations let you extend [code]smith with MCP tools and context from downstream systems. You can delegate issues directly from issue trackers, expand [code]smith’s context with log and observability providers, and search data and metrics in your databases and warehouses.

​
Server scope

Every MCP server in [code]smith has a scope:
  • Personal servers are only available to your [code]smith sessions. Credentials belong to your user account and are not shared with teammates. Teammates can still see the output of these sessions in the session history tab.
  • Team servers are available to every org member’s [code]smith sessions. The organization stores one shared OAuth or API credential, and any teammate’s session uses the same connected account. This is recommended when every user should have the same access level to the underlying tool, or in the case where you’re connecting a service account.
Each session receives team MCPs for the org plus the session owner’s personal MCPs. See Connector permissions for more details.

​
Adding a new MCP server

You can add a new MCP server in one of two ways:
  • Ask [code]smith. From a web session, [code]smith will search the web for the provider and suggest the right input method.
  • Manual configuration. From the new session page, click the “plus” button to manually enter MCP details. You can reconnect or reauthorize MCP servers from the settings page.
You can connect either Remote or Local MCP servers. Local MCP servers will be installed and run on Blacksmith infra in an isolated sandbox. Remote servers connect via OAuth or Headers. Command servers use environment variables to store credentials.

​
Manual configuration steps

1

Open [code]smith settings

In the Blacksmith dashboard, go to your organization’s [code]smith settings.
2

Choose a connection method

For a remote MCP, select an authentication method and provide the remote URL. For installed/local MCP servers, choose “Command” and pass in the command and any associated arguments.
3

Pick the scope

Choose whether the server should be available only to your sessions or to the whole team. If isolation is important, consider provisioning a service account in your backing provider and connecting it as a “Team” MCP.
4

Authorize

For remote servers, complete the OAuth flow or provide the required auth headers for your server. For local servers, provide the command and any necessary environment variables.
5

Test and save

Run the built-in connection test, then save the server. [code]smith can now use it in future sessions - you can disable access to a specific MCP server from the “plus” menu on the new session page.

​
Delegate issues to [code]smith from Linear

You can add [code]smith as a Linear Agent to delegate tasks to. Follow Linear’s instructions for connecting a new Agent. From there you can @ mention or assign [code]smith any ticket and see the resulting PR.