Model Context Protocol (MCP)
Morph IDE natively integrates the Model Context Protocol (MCP), an open architectural standard allowing enterprise engineering teams to safely extend autonomous agent intelligence beyond localized filesystem boundaries.
Connecting External Datasets & APIs
By registering MCP Server connections in your workspace preferences, autonomous agents in Gather and Agent modes gain direct, secure lookup authorization to interact with enterprise infrastructure and external productivity tools in real time during conversation loops:
🗄️Database Schema Introspection
Grant agents read-only MCP access to local development container instances of Postgres, SQLite, MySQL, or MongoDB to inspect live schema tables during development.
🎯Jira & Linear Ticket Tracking
Connect Jira, Linear, or GitHub Issues MCP servers directly to your editor workbench, bringing issue tickets straight into your conversational debugging loops.
@LIN-402). The agent queries Linear via MCP, parses the exact bug reproduction steps and acceptance criteria, and commences codebase bug tracing immediately.📚Internal Wikis & OpenAPI Specs
Provide autonomous agents live lookup access to proprietary company Confluence wikis, microservice OpenAPI / Swagger specifications, or private UI Storybook component catalogs.
Configuring MCP Servers
Connecting an MCP server takes just a few lines in your global or workspace-level settings.json file. Morph IDE supports standard command execution via local Node/Python binaries:
Example Workspace Settings (.vscode/settings.json)
Register independent server definitions under the designated MCP configuration namespace:
{
"morph.mcp.servers": {
"postgres-local": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-postgres", "postgresql://localhost:5432/dev_db"]
},
"linear-issues": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-linear"],
"env": { "LINEAR_API_KEY": "lin_api_secret_key..." }
}
}
}