Skilder

Platform overview

The components Skilder is built from and the boundaries between them.

The control plane stores and authorizes your roles and skills. A separate execution layer runs them.

Components

ComponentResponsibilityBuilt on
Web appAuthoring roles, skills, servers and settingsReact
Control planeIdentity, permissions, the role and skill catalog, OAuth authorizationFastify and Apollo GraphQL
Graph databaseWorkspaces, roles, skills, MCP server definitions, activityDgraph
Message busEvery request that reaches a runtimeNATS, with JetStream for the audit trail
Remote MCP serverThe endpoint agents connect to. Holds sessions and serves Skilder's own tools. Runs no MCP server and no scriptMCP over Streamable HTTP
RuntimeRuns MCP servers and skill scriptsContainer image

How the parts connect

Two boundaries carry the design:

  • The public endpoint and the execution layer are separate containers with separate identities.
  • Every call to one of your MCP servers, and every skill script, crosses the message bus. Skilder's own tools are answered by the endpoint, which calls the control plane over HTTPS. A request for a runtime file goes over the bus to the workspace's own runtime only.
  • The endpoint and each runtime also call the control plane over HTTPS: the endpoint for Skilder's own tools, a runtime to pull its workspace catalog.

Standards

Agents connect over the Model Context Protocol on Streamable HTTP. An MCP client needs no Skilder plugin. Skills follow the Agent Skills standard and import and export as SKILL.md packages. The endpoint also serves MCP Apps: display and analytics results carry an interactive card, served as a ui:// resource, for clients that render one.

Where it runs

Skilder hosts the platform in Switzerland. A runtime can also run on infrastructure you operate, which keeps tool and script execution inside your network.

Next