MCP Servers
Connect external services and tools to your account so the 8090 Software Factory agent can use them.
Connect external services and tools to your 8090 Software Factory account through the Model Context Protocol (MCP). Once a server is connected, the agent can use its tools in your chats, alongside 8090 Software Factory's own tools. Tool permissions decide which of those tools the agent runs on its own, which it asks you about first, and which it never uses.
Browse the catalog
Open Settings → Connections → MCP Servers to see what you can connect. Servers appear in two groups:
| Group | What it is |
|---|---|
| Connected MCP Servers | Servers you have already connected. |
| Available MCP Servers | Everything you can connect, with the servers we recommend for common workflows listed first. |
Recommended servers have a star. Open a server to read its description, or use Search MCP Servers to find a specific service.
Connect a server
Choose a server
Open the server from the catalog, then select Connect in its dialog.
Authorize it
Servers connect one of two ways, and the dialog tells you which one applies:
- Sign-in (OAuth): a new window opens where you sign in to the service and authorize access. It closes when you finish.
- API key: you enter the credentials the service gives you, such as an API key.
A connected server moves to the Connected MCP Servers group. To remove one, open it and select Disconnect.
Connections are personal to you and to the organization you are working in. Teammates don't share them, and if you switch to another organization, you connect the server again there.
Tool permissions
A server's dialog has a Tool Permissions section that controls how the agent may use that server's tools. The tools are split into two groups, each showing how many tools it holds:
| Group | What it holds | Default |
|---|---|---|
| Read-only Tools | Tools the service marks as read-only, such as search and list tools | Allow |
| Action Tools | Every other tool, including tools that create, change, send, or delete | Confirm |
Each group, and each tool in it, takes one of three permissions:
| Permission | What happens |
|---|---|
| Allow | The agent runs the tool without asking. |
| Confirm | The agent asks you before each run, in web chat only. |
| Deny | The agent never sees the tool. |
Set a whole group from the menu next to its name, or expand the group and set tools one by one. Changing a group's permission resets the per-tool settings in that group. When the tools in a group don't all match, the group shows Custom.
Changes save as soon as you make them. Like connections, permissions are yours alone in the current organization. They stay saved if you disconnect a server, so reconnecting it restores them.
How the agent uses your servers
In web chat, the agent can use the tools of every server you have connected, following your tool permissions:
- Allow tools run as soon as the agent calls them.
- Confirm tools show a card titled Run tool in server, with the details the agent wants to send. Select Allow Once to run that one call, or Reject to cancel it. Nothing is sent to the service when you reject.
- Deny tools are hidden from the agent.
Confirm tools need your approval, so they only run in web chat. When you use the agent from Slack, only Allow tools are available.
Automations only use Allow tools
An automation doesn't get your connected servers automatically. To let an automation use a server, grant that server when you set up the automation. No one is there to approve a call during a run, so automations only use tools set to Allow. Action tools start at Confirm, so set the tools an automation needs to Allow first. See Automations.