matimo 0.1.0-alpha.1 → 0.1.0-alpha.2

package/README.md

@@ -69,7 +69,7 @@ You end up duplicating tool logic, schemas, and integrations repeatedly.
 
 I built Matimo because I needed it while working on my own agent product — and I couldn't find a truly framework-agnostic, fully open-source alternative (most are paid or tightly coupled to one framework).
 
-I'm a solo developer (nomadic coder at heart), so this project needs **your help** to become the go-to standard for agent tools.
+I'm a solo developer (nomadic coder at heart) vibe coding, **all help is appriciated** to make matimo a go-to standard for agent tools.
 
 ### How You Can Help Right Now
 
@@ -291,7 +291,8 @@ See [SDK Usage Patterns - Level 2](#level-2-framework-integration-patterns-with-
 **MCP Server (Claude Integration)**
 
 ```typescript
-import { MCPServer } from 'matimo/mcp';
+// MCP Server - Coming in Phase 2
+// import { MCPServer } from 'matimo/mcp';
 
 const server = new MCPServer({
   toolsPath: './tools',
@@ -648,4 +649,4 @@ Contributions are welcome — see [CONTRIBUTING.md](./CONTRIBUTING.md) for guide
 
 **Ready to integrate AI tools across your framework?**
 
-[Get Started Now →](./docs/QUICK_START.md)
+[Get Started Now →](./docs/getting-started/QUICK_START.md)

package/docs/RELEASES.md

@@ -1,3 +1,24 @@
+# v0.1.0-alpha.2
+
+> Improved alpha.1 release - Better npm workflow, fixed exports, accurate feature descriptions
+
+**Released**: February 4, 2026
+
+## What's Improved
+
+### Release & Distribution
+- Fixed npm publish workflow (dist-tag 'next' for pre-releases)
+- Replaced deprecated GitHub Actions (softprops/action-gh-release@v2)
+- Proper semantic versioning for release titles
+- Fixed broken documentation links in releases
+
+### Package & Exports
+- Explicit package exports for main and MCP modules
+- Accurate npm description (reflects current Phase 1 scope)
+- Proper Node.js module resolution
+
+---
+
 # v0.1.0-alpha.1
 
 > First alpha release - Core OAuth2, tool execution, and SDK patterns

package/docs/ROADMAP.md

@@ -122,11 +122,11 @@
 ## Release Thoughts
 
 ```
-v0.1.0-alpha.1  Feb 2026 (Current)
+v0.1.0-alpha.1  Feb 2026.
     ↓
-v0.1.0-alpha.2  3rd week Feb 2026.     
+v0.1.0-alpha.2  Feb 2026 (Current).
     ↓
-v0.1.0-alpha.3  1st week Mar 2026.    
+v0.1.0-alpha.3  Feb 2026.    
     ↓
 v0.1.0     End of March 2026. 
 ```

package/docs/getting-started/QUICK_START.md

@@ -110,7 +110,8 @@ try {
 ### Use with MCP Server
 
 ```typescript
-import { MCPServer } from 'matimo/mcp';
+// MCP Server - Coming in Phase 2
+// import { MCPServer } from 'matimo/mcp';
 
 const server = new MCPServer({
   toolsPath: './tools',

package/docs/index.md

@@ -206,7 +206,8 @@ See [Quick Start](./getting-started/QUICK_START.md) and [API Reference](./api-re
 Matimo can run as an MCP server, allowing Claude and other clients to discover and use tools:
 
 ```typescript
-import { MCPServer } from 'matimo/mcp';
+// MCP Server - Coming in Phase 2
+// import { MCPServer } from 'matimo/mcp';
 
 const server = new MCPServer({ toolsPath: './tools', port: 3000 });
 await server.start();

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "matimo",
-  "version": "0.1.0-alpha.1",
-  "description": "Framework-agnostic YAML-driven tool ecosystem for AI agents. Define tools once in YAML, use them everywhere: SDK, MCP, CLI, REST API.",
+  "version": "0.1.0-alpha.2",
+  "description": "Framework-agnostic YAML-driven tool ecosystem for AI agents. Define tools once in YAML and run them via a TypeScript/JavaScript SDK.",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
   "type": "module",
@@ -10,6 +10,10 @@
     ".": {
       "types": "./dist/index.d.ts",
       "default": "./dist/index.js"
+    },
+    "./mcp": {
+      "types": "./dist/mcp/mcp-server.d.ts",
+      "default": "./dist/mcp/mcp-server.js"
     }
   },
   "engines": {