Skip to main content

MCP Server

Smartloop supports the Model Context Protocol (MCP), allowing you to enrich your assistant with external tools and data sources.

Getting Started​

When a new project is created, we automatically configure the following MCPs:

  • fetch
  • file-read
  • file-write
  • bash

These are used as baseline or system MCPs to improve the experience. For example, whenever you paste a URL in the chat and ask it to extract information from it, it uses fetch to do so.

alt text

Making It Work​

MCP servers can be used with skills — more details in the skills section — but it is possible to configure a skill to select an MCP tool. For example, here is a basic example of create-issue:

When the user requests to create an issue, use the title and description, then make a tool call to save_issue on the Linear MCP to save it, using team=DEV.

Find the tool in Linear MCP and execute it with the following arguments:
- title
- description
- team

Confirm that the tool returned successfully.

Configuration​

To configure an MCP server, go to the Skills tab in the studio and paste the link. In this case, Linear MCP is used as an example, but you can use any remote MCP endpoint that supports the latest specification.

An MCP server can be one of the following types when working with the studio app:

  • open — requires no authentication
  • authenticated — requires authentication, generally OAuth-based

alt text