Building Custom Connections

Note: Building custom connections requires technical expertise in software development. This guide assumes familiarity with API development and deployment.

---

What are Custom Connections?

Custom connections allow you to connect Duvo to systems that aren't covered by a standard Duvo connection. Think of them as custom-built bridges between DUVO and your proprietary or specialized software.

---

Building A Custom Connection

Duvo uses the Model Context Protocol (MCP) open standard to connect with external systems—it's not a Duvo product. To build your own MCP server to create custom tools for your assignments, you'll need technical expertise in software development.

If you're not familiar with MCP, visit the official MCP documentation at https://modelcontextprotocol.io/docs/getting-started/intro. This resource provides comprehensive guides, tutorials, and examples for building MCP servers in various programming languages.

Once you have built, tested, and deployed an MCP server, you can connect it to Duvo using the steps outlined in "How to Add a Connection".

---

Requirements for Custom Connections

For your MCP server to connect to Duvo it must meet these technical requirements:

Cloud accessibility: The MCP server must be accessible via the internet (cloud-hosted). Duvo needs to reach it over the web to communicate.

Streamable HTTP: The MCP server must support streamable HTTP communication. MCP servers that only support STDIO (standard input/output) or HTTP/SSE won't be able to connect to Duvo's assignments.