MCP

The Model Context Protocol (MCP) lets agents use tools and data from other apps: issues, databases, design files, docs. Ingot speaks MCP protocol version 2025-06-18 and gives each server 15 seconds to answer.

The marketplace

Open the MCP tool window to browse 22 one-click servers: GitHub, GitLab, Jira & Confluence, Linear, Slack, Notion, Figma, Postgres, Supabase, Neon, Sentry, Vercel, Stripe, Resend, Discord, Google Drive, Gmail, Playwright, Docker, Filesystem, Fetch and Memory.

Pick one and Ingot writes the configuration for you. If the server needs a token, Ingot asks for it once and stores it in your operating system's keychain. Servers that sign in with OAuth open your browser once.

mcp.json

Existing mcp.json files from other tools are read as they are.

{
  "mcpServers": {
    "postgres": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-postgres"],
      "env": { "DATABASE_URL": "${keychain}" }
    },
    "docs": {
      "url": "https://mcp.example.com/sse",
      "headers": { "Authorization": "${keychain}" }
    }
  }
}

Secrets stay out of Git

A value of "${keychain}" means "read this from the OS keychain". The real token never touches mcp.json, so the file is safe to commit and share with your team; each teammate enters their own token once.