skippy-mcp 0.2.0__tar.gz

skippy_mcp-0.2.0/.gitignore

@@ -0,0 +1,4 @@
+.venv/
+dist/
+__pycache__/
+*.egg-info/

skippy_mcp-0.2.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Sanvio Labs
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

skippy_mcp-0.2.0/PKG-INFO

@@ -0,0 +1,130 @@
+Metadata-Version: 2.5
+Name: skippy-mcp
+Version: 0.2.0
+Summary: Use Skippy from Claude, Cursor, Kiro and any other MCP client. Private beta.
+Project-URL: Homepage, https://heyskippy.ai
+Author: Sanvio Labs
+License-Expression: MIT
+License-File: LICENSE
+Keywords: ai-assistant,mcp,model-context-protocol,skippy
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Requires-Python: >=3.10
+Requires-Dist: httpx>=0.27.0
+Requires-Dist: mcp<2,>=1.0.0
+Description-Content-Type: text/markdown
+
+# Skippy MCP
+
+Use Skippy from Claude, Cursor, Kiro, VS Code, or any other MCP client. Your notes, workspace, skills, agents and research live in Skippy, so what you save in one tool is there in the next.
+
+**This is a private beta.** Your Skippy account has to be added to it first. If you haven't been invited, ask the Skippy team.
+
+## Setup
+
+You need two things: a Skippy account in the beta, and [uv](https://docs.astral.sh/uv/getting-started/installation/) installed. Setup takes about five minutes.
+
+### 1. Create an API key
+
+In Skippy, open **Settings > API Keys** and click **Create new key**. Copy it straight away: Skippy shows it once.
+
+### 2. Save the key
+
+```bash
+uvx skippy-mcp auth
+```
+
+Paste the key when it asks. It saves the key to `~/.skippy/token`, readable only by you, then checks it with Skippy. You should see `✓ Key works.`
+
+### 3. Add Skippy to your client
+
+Every client runs the same command, `uvx skippy-mcp`. Only where you put it changes.
+
+**Claude Code**
+
+```bash
+claude mcp add skippy -- uvx skippy-mcp
+```
+
+**Claude Desktop, Cursor, Kiro and Windsurf** take this block:
+
+```json
+{
+  "mcpServers": {
+    "skippy": {
+      "command": "uvx",
+      "args": ["skippy-mcp"]
+    }
+  }
+}
+```
+
+| Client | Where it goes |
+|---|---|
+| Claude Desktop | `~/Library/Application Support/Claude/claude_desktop_config.json` on macOS, `%APPDATA%\Claude\claude_desktop_config.json` on Windows |
+| Cursor | `~/.cursor/mcp.json` for every project, or `.cursor/mcp.json` for one |
+| Kiro | `~/.kiro/settings/mcp.json` for every project, or `.kiro/settings/mcp.json` for one |
+| Windsurf | `~/.codeium/windsurf/mcp_config.json` |
+
+**VS Code** uses a slightly different shape, in `.vscode/mcp.json`:
+
+```json
+{
+  "servers": {
+    "skippy": {
+      "type": "stdio",
+      "command": "uvx",
+      "args": ["skippy-mcp"]
+    }
+  }
+}
+```
+
+Restart the client. Ask it to run `skippy_status`, and you should see your name and plan.
+
+## What you can do
+
+| Ask for | Tools |
+|---|---|
+| A conversation with Skippy, with its memory of you | `skippy_send`, `skippy_context` |
+| Research | `skippy_web_search`, `skippy_deep_research` |
+| Your files in Skippy | `skippy_workspace_read`, `_write`, `_list`, `_delete` |
+| Notes and a clipboard that follow you between tools | `skippy_save_note`, `skippy_view_notes`, `skippy_clip`, `skippy_paste` |
+| A searchable log of decisions and milestones | `skippy_journal`, `skippy_journal_search` |
+| Saved workflows | `skippy_create_skill`, `skippy_run_skill`, `skippy_list_skills` |
+| Your agents | `skippy_list_agents`, `skippy_invoke_agent`, `skippy_create_agent` |
+| Scheduled jobs | `skippy_schedule_job`, `skippy_list_jobs`, `skippy_cancel_job` |
+| Topics Skippy watches for you | `skippy_radar_add_topic`, `skippy_radar_scan` |
+| Static sites | `skippy_publish_site`, `skippy_share_site`, `skippy_list_sites` |
+| Your usage | `skippy_usage` |
+
+Deep research draws on the same monthly research credits as the Skippy app.
+
+Four tools run on your own machine instead: `read_local_file`, `list_local_files`, `git_status` and `git_diff`. They can only see the folder your client started the server in. What they read goes to your AI client, the same as any file you open in it, and none of it goes to Skippy.
+
+## Troubleshooting
+
+**"The Skippy MCP server is in private beta."** Your key works, but your account isn't in the beta yet. Ask the Skippy team to add you.
+
+**"This key is invalid or disabled."** The key was revoked, disabled, or mistyped. Create a new one under Settings > API Keys and run `uvx skippy-mcp auth` again.
+
+**Your client says it can't find `uvx`.** Desktop apps often start with a shorter `PATH` than your terminal. Run `which uvx` in a terminal and put that full path in `"command"` instead of `uvx`.
+
+**To check your setup at any time**, run `uvx skippy-mcp verify`.
+
+## Folder-based scoping (optional)
+
+If you keep work for different clients or projects in different folders, Skippy can file workspace writes and journal entries under that name automatically. Create `~/.skippy/client_map.json`:
+
+```json
+{ "/work/northwind": "northwind", "/work/contoso": "contoso" }
+```
+
+When the server starts in a folder whose path contains one of those fragments, `notes.md` is saved as `clients/northwind/notes.md`. The `SKIPPY_CLIENT_MAP` environment variable takes the same JSON and overrides the file. With neither, nothing is scoped.
+
+## Feedback
+
+Something broken or missing? Ask your client to run `skippy_submit_feedback`. It goes straight to the team building Skippy.

skippy_mcp-0.2.0/README.md

@@ -0,0 +1,111 @@
+# Skippy MCP
+
+Use Skippy from Claude, Cursor, Kiro, VS Code, or any other MCP client. Your notes, workspace, skills, agents and research live in Skippy, so what you save in one tool is there in the next.
+
+**This is a private beta.** Your Skippy account has to be added to it first. If you haven't been invited, ask the Skippy team.
+
+## Setup
+
+You need two things: a Skippy account in the beta, and [uv](https://docs.astral.sh/uv/getting-started/installation/) installed. Setup takes about five minutes.
+
+### 1. Create an API key
+
+In Skippy, open **Settings > API Keys** and click **Create new key**. Copy it straight away: Skippy shows it once.
+
+### 2. Save the key
+
+```bash
+uvx skippy-mcp auth
+```
+
+Paste the key when it asks. It saves the key to `~/.skippy/token`, readable only by you, then checks it with Skippy. You should see `✓ Key works.`
+
+### 3. Add Skippy to your client
+
+Every client runs the same command, `uvx skippy-mcp`. Only where you put it changes.
+
+**Claude Code**
+
+```bash
+claude mcp add skippy -- uvx skippy-mcp
+```
+
+**Claude Desktop, Cursor, Kiro and Windsurf** take this block:
+
+```json
+{
+  "mcpServers": {
+    "skippy": {
+      "command": "uvx",
+      "args": ["skippy-mcp"]
+    }
+  }
+}
+```
+
+| Client | Where it goes |
+|---|---|
+| Claude Desktop | `~/Library/Application Support/Claude/claude_desktop_config.json` on macOS, `%APPDATA%\Claude\claude_desktop_config.json` on Windows |
+| Cursor | `~/.cursor/mcp.json` for every project, or `.cursor/mcp.json` for one |
+| Kiro | `~/.kiro/settings/mcp.json` for every project, or `.kiro/settings/mcp.json` for one |
+| Windsurf | `~/.codeium/windsurf/mcp_config.json` |
+
+**VS Code** uses a slightly different shape, in `.vscode/mcp.json`:
+
+```json
+{
+  "servers": {
+    "skippy": {
+      "type": "stdio",
+      "command": "uvx",
+      "args": ["skippy-mcp"]
+    }
+  }
+}
+```
+
+Restart the client. Ask it to run `skippy_status`, and you should see your name and plan.
+
+## What you can do
+
+| Ask for | Tools |
+|---|---|
+| A conversation with Skippy, with its memory of you | `skippy_send`, `skippy_context` |
+| Research | `skippy_web_search`, `skippy_deep_research` |
+| Your files in Skippy | `skippy_workspace_read`, `_write`, `_list`, `_delete` |
+| Notes and a clipboard that follow you between tools | `skippy_save_note`, `skippy_view_notes`, `skippy_clip`, `skippy_paste` |
+| A searchable log of decisions and milestones | `skippy_journal`, `skippy_journal_search` |
+| Saved workflows | `skippy_create_skill`, `skippy_run_skill`, `skippy_list_skills` |
+| Your agents | `skippy_list_agents`, `skippy_invoke_agent`, `skippy_create_agent` |
+| Scheduled jobs | `skippy_schedule_job`, `skippy_list_jobs`, `skippy_cancel_job` |
+| Topics Skippy watches for you | `skippy_radar_add_topic`, `skippy_radar_scan` |
+| Static sites | `skippy_publish_site`, `skippy_share_site`, `skippy_list_sites` |
+| Your usage | `skippy_usage` |
+
+Deep research draws on the same monthly research credits as the Skippy app.
+
+Four tools run on your own machine instead: `read_local_file`, `list_local_files`, `git_status` and `git_diff`. They can only see the folder your client started the server in. What they read goes to your AI client, the same as any file you open in it, and none of it goes to Skippy.
+
+## Troubleshooting
+
+**"The Skippy MCP server is in private beta."** Your key works, but your account isn't in the beta yet. Ask the Skippy team to add you.
+
+**"This key is invalid or disabled."** The key was revoked, disabled, or mistyped. Create a new one under Settings > API Keys and run `uvx skippy-mcp auth` again.
+
+**Your client says it can't find `uvx`.** Desktop apps often start with a shorter `PATH` than your terminal. Run `which uvx` in a terminal and put that full path in `"command"` instead of `uvx`.
+
+**To check your setup at any time**, run `uvx skippy-mcp verify`.
+
+## Folder-based scoping (optional)
+
+If you keep work for different clients or projects in different folders, Skippy can file workspace writes and journal entries under that name automatically. Create `~/.skippy/client_map.json`:
+
+```json
+{ "/work/northwind": "northwind", "/work/contoso": "contoso" }
+```
+
+When the server starts in a folder whose path contains one of those fragments, `notes.md` is saved as `clients/northwind/notes.md`. The `SKIPPY_CLIENT_MAP` environment variable takes the same JSON and overrides the file. With neither, nothing is scoped.
+
+## Feedback
+
+Something broken or missing? Ask your client to run `skippy_submit_feedback`. It goes straight to the team building Skippy.

skippy_mcp-0.2.0/pyproject.toml

@@ -0,0 +1,68 @@
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[project]
+name = "skippy-mcp"
+version = "0.2.0"
+description = "Use Skippy from Claude, Cursor, Kiro and any other MCP client. Private beta."
+readme = "README.md"
+requires-python = ">=3.10"
+license = "MIT"
+license-files = ["LICENSE"]
+authors = [{ name = "Sanvio Labs" }]
+keywords = ["mcp", "skippy", "model-context-protocol", "ai-assistant"]
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Environment :: Console",
+    "Intended Audience :: Developers",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3",
+]
+dependencies = [
+    # `<2` is load-bearing, not caution. mcp 2.0 renamed FastMCP to MCPServer and
+    # moved `mcp.server.fastmcp`, so `server.py` does not import under it. The dev
+    # environment resolves through uv.lock and never saw this; a published package
+    # ignores the lock, so `uvx skippy-mcp serve` picked up 2.x and traced back on
+    # the one command the tool exists for. Measured 2026-09-19 against a wheel
+    # installed into an empty venv.
+    "mcp>=1.0.0,<2",
+    "httpx>=0.27.0",
+]
+
+[project.urls]
+Homepage = "https://heyskippy.ai"
+
+[project.scripts]
+skippy-mcp = "skippy_mcp.cli:main"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/skippy_mcp"]
+
+# The sdist carries the package and nothing else: no tests, no lockfile, nothing
+# written for the people who build Skippy rather than the people who use it.
+[tool.hatch.build.targets.sdist]
+include = ["src/skippy_mcp", "README.md", "LICENSE", "pyproject.toml"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+python_files = ["test_*.py"]
+python_classes = ["Test*"]
+python_functions = ["test_*"]
+addopts = "-v --tb=short"
+
+[dependency-groups]
+dev = [
+    "pytest>=8.0",
+    "pytest-mock>=3.14",
+]
+
+[tool.ruff]
+line-length = 120
+
+[tool.ruff.lint]
+select = ["E", "W", "F", "I", "B", "UP"]
+ignore = ["E501"]
+
+[tool.ruff.lint.per-file-ignores]
+"tests/**" = ["S101", "S106", "S108", "F841"]

skippy_mcp-0.2.0/src/skippy_mcp/__init__.py

@@ -0,0 +1,3 @@
+"""Skippy MCP server: use Skippy from Claude, Cursor, Kiro and other MCP clients."""
+
+__version__ = "0.2.0"