@spacholski1225/anki-connect-mcp 1.0.4 → 1.0.5

package/README.md

@@ -125,6 +125,8 @@ To use this MCP server with Claude Desktop, add the following configuration to y
 ```
 
 #### Option 2: Using npx (NPM Package)
+
+**Then configure your MCP client:**
 ```json
 {
   "mcpServers": {
@@ -209,13 +211,6 @@ When using the Docker option, you **must** configure AnkiConnect with specific s
 - Make sure Anki is running with AnkiConnect enabled before using the MCP server
 - For Docker option, the `--network=host` flag allows the container to access AnkiConnect on the host machine
 
-### Other MCP Clients
-
-For other MCP clients, use the following connection details:
-- **Transport**: stdio
-- **Command**: `node dist/index.js`
-- **Working Directory**: Path to this repository
-
 ## Usage Examples
 
 Once configured with an MCP client like Claude Desktop, you can interact with your Anki collection naturally:
@@ -226,70 +221,6 @@ Once configured with an MCP client like Claude Desktop, you can interact with yo
 - *"Suspend all cards in the 'Difficult Words' deck"*
 - *"Open the deck browser in Anki"*
 
-## Development
-
-### Project Structure
-
-```
-src/
-├── index.ts              # Main MCP server setup and tool definitions
-├── methods/
-│   └── anki.ts          # AnkiConnect API communication
-├── tools/               # Tool implementations
-│   ├── cards.ts         # Card-related operations
-│   ├── decks.ts         # Deck management
-│   ├── misc.ts          # Utility functions and GUI controls
-│   ├── models.ts        # Note type operations
-│   └── notes.ts         # Note management
-└── types/               # TypeScript type definitions
-    └── anki/            # AnkiConnect API types
-```
-
-### Available Scripts
-
-- `npm run build` - Compile TypeScript to JavaScript
-- `npm start` - Run the compiled MCP server
-- `npm test` - Run tests (not implemented yet)
-
-## Docker Deployment
-
-### Building and Running with Docker
-
-1. **Build the Docker image**:
-```bash
-docker build -t anki-connect-mcp .
-```
-
-2. **Run with default settings** (connects to AnkiConnect on localhost:8765):
-```bash
-docker run -d --name anki-connect-mcp anki-connect-mcp
-```
-
-3. **Run with custom AnkiConnect URL**:
-```bash
-docker run -d --name anki-connect-mcp -e ANKI_CONNECT_URL=http://custom-host:8765 anki-connect-mcp
-```
-
-### Using Docker Compose
-
-1. **Start the service**:
-```bash
-docker-compose up -d
-```
-
-2. **Stop the service**:
-```bash
-docker-compose down
-```
-
-### Environment Variables
-
-- `ANKI_CONNECT_URL`: The URL where AnkiConnect is running (default: `http://localhost:8765`)
-
-### Docker Configuration for MCP Clients
-
-When using Docker, update your MCP client configuration to use the containerized version. The exact configuration depends on your setup, but you may need to adjust network settings to allow the MCP client to communicate with the Docker container.
-
 ## Troubleshooting
 
 ### Common Issues
@@ -299,10 +230,6 @@ When using Docker, update your MCP client configuration to use the containerized
 3. **Permission errors**: Ensure the MCP server has proper file system permissions
 4. **Tool not found**: Verify the MCP client configuration and restart the client
 
-### Debug Mode
-
-To enable debug logging, check the console output when running the MCP server. All AnkiConnect requests and responses are logged for troubleshooting.
-
 ## Contributing
 
 Contributions are welcome! Please feel free to submit issues, feature requests, or pull requests.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@spacholski1225/anki-connect-mcp",
-  "version": "1.0.4",
+  "version": "1.0.5",
   "description": "MCP server for Anki Connect integration",
   "main": "dist/index.js",
   "bin": {
@@ -43,6 +43,7 @@
   },
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.12.1",
+    "@spacholski1225/anki-connect-mcp": "^1.0.4",
     "axios": "^1.9.0"
   }
 }