Skip to content
Swytchcode logo Swytchcode logo Swytchcode Docs

Getting started

Swytchcode provides three powerful interfaces that work together to help you manage, test, and deliver API integrations faster:

1. Web Application
2. Web Plugin
3. MCP Server

Each serves a distinct purpose and is designed to plug into your team’s workflow seamlessly. Here’s how they work together.

Video Walkthrough

Want a quick overview before diving into the details? Watch this short video to see how to get started with Swytchcode in minutes:

This video walks you through the basics of connecting, exploring methods, and running your first workflow with Swytchcode.

Web Application

The Swytchcode web app is your main control panel — where you:

  • Upload OpenAPI/Postman specs or SDK files
  • Organize APIs and SDKs into libraries and projects
  • Manage API keys and usage permissions
  • View analytics for code generation, testing, and plugin usage
  • Monitor SDK coverage and developer interaction

It’s the central hub where admins, solutions engineers, or API owners configure what gets exposed to users and how it behaves.

Web Plugin

The Swytchcode plugin is an embeddable, interactive UI component — used by developers, partners, or internal teams to:

  • Explore available API methods
  • Generate production-grade code in multiple languages
  • Ask contextual questions about schemas or usage
  • Test and mock API methods with zero setup
  • Search, sort, and filter through methods/workflows
  • Manage MCP keys to interact with Swythcode MCP server

You can embed this plugin in your docs site, developer portal, or even internal sandboxes. It brings the API experience directly to where developers work — no login or tool switching needed.

MCP Server (Model Context Protocol)

The MCP server powers Swytchcode’s intelligence layer to interact with AI agents

It understands your API surface area — methods, parameters, schemas, auth requirements, and workflows — and feeds this context to AI models. It can

  • Generate accurate, real-world integration code
  • Answer schema-related questions in plain language
  • List all libraries, methods and workflows

The MCP server is maintained alongside your API/SDK definitions and stays up-to-date as your specs evolve.

How It All Works Together

Here’s how the three components connect:

  • Start in the Web App: upload your OpenAPI spec or SDKs, configure method visibility, and enable MCP for that project/library.

  • Embed the Plugin: Drop the web plugin into your docs, partner portal, or internal dashboard. Users can now explore, test, and generate code instantly — with full MCP context behind the scenes.

  • MCP Server: Generate an MCP key from the plugin and Swytchcode processes your API enables MCP for you.

  • Monitor & Iterate: Use the Web App’s dashboard to track what’s being used, which methods are being tested, and how developers are interacting with your APIs. Iterate and improve based on real-world signals.