Smia

io.github.Smia-Technologies-ASv1.0.0Updated Oct 8, 2026

Build your own tools from chat: design, test and host them on a shareable MCP server URL.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Lets an assistant design, test, and host custom tools from chat, publishing them on a shareable MCP server URL.

What it does
Smia is a remote MCP server that lets an assistant build its own tools directly from a conversation. According to the registry description, it supports designing, testing, and hosting those tools, and exposes them through a shareable MCP server URL. No individual tools are listed in the manifest, so the exact tool set is not documented here.
When to use it
Consider it when you want an assistant to create and host custom tools from chat rather than only call pre-built ones, and when a hosted, shareable MCP endpoint fits your workflow. It is less relevant if you only need existing tools or a locally run server.
Requirements
Remote streamable HTTP endpoint at No packages, environment variables, or headers are declared, and the manifest declares no authentication.
Before you install
The manifest declares no authentication, so anyone with the endpoint URL may be able to reach it; treat the URL as sensitive. Tools are created and hosted on a third-party service, so anything you build or send there leaves your machine. No credentials, payments, or write actions are documented in the input.

Installation

In SourceWeft

  1. Open Smia in the dashboard and add it to a workspace.
  2. 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.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "smia": {
      "type": "http",
      "url": "https://app.smia.io/mcp?src=mcp-registry"
    }
  }
}

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.0.0LatestOct 8, 2026