Skilder

ai.skilderPublished by skilder.aiOfficial publisherv0.10.2Updated Oct 24, 2026

One place to build, share, and govern the skills and tools your AI agents use at work.

VerifiedStreamable HTTPWeb executableAI & ML

Overview

AI-generated overview

Skilder is a remote MCP endpoint for building, sharing and governing the skills and tools that AI agents use at work.

What you can do
The manifest lists no tools, so capabilities are known only from the registry description. It is presented as a single place to build skills and tools for AI agents. It also covers sharing those skills and tools, and governing how they are used at work. It connects as a remote endpoint rather than a local package.
When to use it
Consider it when you want a shared, governed home for the skills and tools your AI agents rely on, rather than managing them separately per assistant. It suits teams that need to distribute agent capabilities across people.
Requirements
A remote MCP connection to the provider's hosted endpoint over streamable HTTP. Authentication is required and uses OAuth, so you need an account with the provider and a client that supports OAuth sign-in. No environment variables or headers are declared.
Before you install
The server requires OAuth sign-in, so you grant it access to your provider account; review the scopes requested during authorization. The manifest lists no tools, so what it can read or change cannot be verified from this listing. Because it governs shared agent skills and tools, changes may affect other users in your workspace.

Installation

In SourceWeft

  1. Open Skilder in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.skilder%2Fskilder/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "skilder": {
      "type": "http",
      "url": "https://app.skilder.ai/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.10.2LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.