snapy-mcp 1.0.0

package/README.md

@@ -0,0 +1,36 @@
+# snapy-mcp
+
+An MCP server that gives an AI assistant (Claude and other MCP clients) a `publish` tool. The assistant can publish text or HTML to snapy and get back a shareable link.
+
+## Use it
+
+Add this to your MCP client config (for example Claude Desktop):
+
+```json
+{
+  "mcpServers": {
+    "snapy": {
+      "command": "npx",
+      "args": ["-y", "snapy-mcp"],
+      "env": { "SNAPY_API_KEY": "snapy_live_..." }
+    }
+  }
+}
+```
+
+Or run it directly from this folder:
+
+```
+npm install
+node index.js
+```
+
+The tool calls the public snapy publish API at `https://api.snapy.host`. Set `SNAPY_API` to override.
+
+## Tool
+
+- **publish** — args: `content` (required text/HTML), `name` (optional link name), `filename` (optional, default index.html). Returns the live link and a private analytics link.
+
+## The API key
+
+Publishing a **web page** needs an API key. Create one in your snapy dashboard under **API keys** and pass it as `SNAPY_API_KEY`. Plain text formats (`.txt`, `.md`, `.csv`, `.json`) publish without one, so the connector works with no setup and gains page publishing when a key is present.

package/index.js

@@ -0,0 +1,75 @@
+#!/usr/bin/env node
+// snapy MCP server: gives an assistant (Claude, etc.) a "publish" tool that uploads
+// text or HTML to snapy and returns a shareable link. Talks to the public publish API.
+import { Server } from "@modelcontextprotocol/sdk/server/index.js";
+import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
+import { CallToolRequestSchema, ListToolsRequestSchema } from "@modelcontextprotocol/sdk/types.js";
+
+const API = process.env.SNAPY_API || "https://api.snapy.host";
+
+// Publishing a web page needs an API key; plain text formats do not. Left optional
+// so the connector still works with no setup at all, and gains page publishing the
+// moment a key is present. Create one in the Snapy dashboard under API keys.
+const API_KEY = process.env.SNAPY_API_KEY || "";
+
+const server = new Server(
+  { name: "snapy", version: "1.0.0" },
+  { capabilities: { tools: {} } }
+);
+
+server.setRequestHandler(ListToolsRequestSchema, async () => ({
+  tools: [
+    {
+      name: "publish",
+      description:
+        "Publish text or HTML content to snapy and get back a shareable link that opens in any browser. Use this to host a page or file you created and return the link.",
+      inputSchema: {
+        type: "object",
+        properties: {
+          content: { type: "string", description: "The text or HTML to publish." },
+          name: { type: "string", description: "Optional custom link name (the subdomain)." },
+          filename: { type: "string", description: "Optional file name, defaults to index.html." },
+        },
+        required: ["content"],
+      },
+    },
+  ],
+}));
+
+server.setRequestHandler(CallToolRequestSchema, async (req) => {
+  if (req.params.name !== "publish") {
+    return { content: [{ type: "text", text: "Unknown tool" }], isError: true };
+  }
+  const { content, name, filename } = req.params.arguments || {};
+  try {
+    const headers = { "content-type": "application/json" };
+    if (API_KEY) headers.authorization = `Bearer ${API_KEY}`;
+    const res = await fetch(`${API}/api/publish`, {
+      method: "POST",
+      headers,
+      body: JSON.stringify({ content, name, filename }),
+    });
+    const data = await res.json();
+    if (!res.ok) {
+      // The most likely failure by far: publishing a page with no key set. The API's
+      // own message is clearer than anything generic, so pass it through and add the
+      // one instruction it cannot know, which is where the key comes from.
+      const hint = !API_KEY && (res.status === 401 || res.status === 403)
+        ? " Set SNAPY_API_KEY to publish a web page: create a key in your Snapy dashboard under API keys."
+        : "";
+      return {
+        content: [{ type: "text", text: "snapy error: " + (data.error || res.status) + hint }],
+        isError: true,
+      };
+    }
+    return {
+      content: [{ type: "text", text: `Published. Link: ${data.url}\nPrivate analytics: ${data.stats_url}` }],
+    };
+  } catch (e) {
+    return { content: [{ type: "text", text: "Request failed: " + e.message }], isError: true };
+  }
+});
+
+const transport = new StdioServerTransport();
+await server.connect(transport);
+console.error("snapy MCP server running on stdio");

package/package.json

@@ -0,0 +1,25 @@
+{
+  "name": "snapy-mcp",
+  "version": "1.0.0",
+  "description": "MCP server to publish files and pages to snapy and get a shareable link.",
+  "homepage": "https://snapy.host/integrations/mcp",
+  "keywords": [
+    "mcp",
+    "modelcontextprotocol",
+    "snapy",
+    "publish",
+    "hosting",
+    "claude",
+    "ai"
+  ],
+  "type": "module",
+  "bin": {
+    "snapy-mcp": "index.js"
+  },
+  "engines": {
+    "node": ">=18"
+  },
+  "dependencies": {
+    "@modelcontextprotocol/sdk": "^1.0.0"
+  }
+}