The Developer MCP Server: AI-Powered Development From Your IDE

Life Savor Engineering
developer mcp tooling

Building components for Life Savor means working with manifests, build pipelines, bridge protocols, and platform APIs. The Developer MCP Server puts all of that directly in your IDE — no context switching, no browser tabs, no copy-pasting between docs and code.

What Is It?

The Developer MCP Server is a hosted service that implements the Model Context Protocol. You connect to it from any MCP-compatible IDE (VS Code, Cursor, Windsurf, Claude Desktop) and get access to 40+ tools for building, debugging, and managing your components — all without leaving your editor.

It's like having a platform expert sitting next to you who can scaffold projects, validate your manifests, check build status, search documentation, and explain how things work.

Setting It Up

Add this to your IDE's MCP configuration:

{
  "mcpServers": {
    "lifesavor-developer": {
      "url": "https://mcp.developer.lifesavor.ai/sse",
      "headers": {
        "Authorization": "Bearer lsk_your_api_key_here"
      }
    }
  }
}

That's it. Your IDE connects, authenticates with your API key, and you have access to the full toolset.

What You Can Do

Scaffold Components Instantly

Instead of reading docs and creating files manually:

"Scaffold a new Python skill called weather-lookup"

The server generates the complete project structure — manifest, entrypoint, configuration schema, build config — ready to customize.

Validate Before You Submit

Catch manifest errors before they hit the build pipeline:

"Validate my manifest"

The server checks your TOML for syntax errors, missing fields, invalid values, and returns actionable fixes. It can even auto-fix common issues.

Debug Bridge Protocol Issues

When your skill isn't communicating correctly with system components:

"Diagnose bridge error COMPONENT_TIMEOUT"

You get a structured diagnosis: what the error means, common causes, diagnostic steps, and links to relevant documentation.

"Explain the bridge flow for a skill calling the summarize operation"

Step-by-step breakdown of the dispatch flow, including timeouts and possible error codes at each stage.

Check Build Status Without Leaving Your Editor

"Show me my recent builds"

"Get the logs for my latest failed build"

No more switching to the portal to check if your build passed. The server pulls live data from the platform.

Search Documentation Semantically

"How do I handle validation commands in a setup step?"

The server uses semantic search over the full SDK documentation. It doesn't just keyword-match — it understands what you're asking and returns the most relevant sections.

AI-Powered Explanations

"Explain how the bridge dispatch works"

"What's the component lifecycle?"

The server uses retrieval-augmented generation (RAG) to give you accurate, documentation-grounded explanations. It pulls relevant docs, then generates a clear answer — no hallucination, no outdated information.

Generate Code

"Generate a bridge request handler for the summarize and translate operations"

"Generate test stubs for my skill's validate_credentials operation"

The server produces handler skeletons and test stubs tailored to your component type and language, following platform conventions.

Manage Components

"Create a new skill component called data-enricher"

"Update my component's description and tags"

"Submit my component for review"

"Connect my GitHub repo"

Full component lifecycle management without touching the CLI or portal.

How It Speeds Up Development

Before the MCP server:

  1. Open browser → navigate to docs → search for the right page
  2. Read the docs → switch back to IDE → write code
  3. Open terminal → run CLI commands → check output
  4. Open portal → check build status → read logs
  5. Back to IDE → fix the issue → repeat

With the MCP server:

  1. Ask your IDE → get the answer → write code → validate → submit

Everything happens in one place. Your AI assistant has full context about the platform, your components, your builds, and the documentation. It can answer questions, generate code, and take actions — all in the flow of your work.

What's Under the Hood

The MCP server is a hosted Node.js service that:

  • Authenticates via your existing API key (lsk_ prefix) or OAuth
  • Delegates data operations to the Developer API (single source of truth)
  • Uses Amazon Bedrock + Knowledge Bases for semantic search and AI features
  • Maintains session state (active component, language preference) in Redis
  • Scales horizontally behind an ALB with sticky sessions for SSE

Your data is isolated — you can only access your own components, builds, and logs. The server enforces ownership checks on every request.

Getting Started

  1. Generate an API key at developer.lifesavor.ai/api-keys
  2. Add the MCP server config to your IDE
  3. Start asking questions

The server works with any MCP-compatible client. If your IDE supports MCP, it supports the Life Savor Developer Server.

Try it: ask it to scaffold your first component, then validate the manifest, then explain how to add a configuration schema. The whole flow happens in your editor.