JSPM

templation-mcp-server

1.0.0
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • 0
  • Score
    100M100P100Q13399F
  • License MIT

MCP server for Templation - Transform GitHub repositories into personalized templates

Package Exports

  • templation-mcp-server
  • templation-mcp-server/dist/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (templation-mcp-server) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Templation MCP Server

Transform GitHub repositories into personalized templates with AI assistance directly in Cursor or Claude Desktop.

๐Ÿš€ Quick Setup

1. Install the MCP Server

# Install globally via npm
npm install -g @templation/mcp-server

# Or if you prefer to run from source:
git clone https://github.com/your-username/templation.git
cd templation/mcp-server
npm install
npm run build

2. Get Your API Key

  1. Go to Templation Web App
  2. Sign in with Auth0
  3. Navigate to Account โ†’ API Keys tab
  4. Click Create New Key and give it a name (e.g., "MCP Server")
  5. Copy the API key (it will only be shown once!)

3. Configure Claude Desktop

Create or edit your Claude Desktop configuration file:

macOS: ~/.config/claude-desktop/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

Add this configuration:

{
  "mcpServers": {
    "templation": {
      "command": "npx",
      "args": ["@templation/mcp-server"],
      "env": {
        "TEMPLATION_API_KEY": "your_api_key_here",
        "TEMPLATION_API_URL": "https://templation-backend.up.railway.app"
      }
    }
  }
}

4. Configure Cursor (Alternative)

If you're using Cursor, add this to your Cursor settings:

{
  "mcp": {
    "servers": {
      "templation": {
        "command": "npx",
        "args": ["@templation/mcp-server"],
        "env": {
          "TEMPLATION_API_KEY": "your_api_key_here",
          "TEMPLATION_API_URL": "https://templation-backend.up.railway.app"
        }
      }
    }
  }
}

5. Restart and Test

  1. Restart Claude Desktop or Cursor
  2. Open a new conversation
  3. Try these commands:
Can you get my user info from Templation?
Show me my dashboard statistics
Search for React templates

๐Ÿ›  Available Functions

search_templates

Search your saved templates by name or description.

Example: "Search for React portfolio templates"

get_user_info

Get information about your Templation account.

Example: "What's my user info?"

get_dashboard_stats

Get your dashboard statistics (templates, repositories, etc.).

Example: "Show me my dashboard stats"

๐Ÿ”ง Troubleshooting

"API key not configured" Error

  • Make sure you've set the TEMPLATION_API_KEY environment variable
  • Verify the API key is correct (create a new one if needed)

"Server failed to start" Error

  • Check that Node.js is installed (node --version)
  • Make sure the package is installed (npm list -g @templation/mcp-server)
  • Try reinstalling: npm install -g @templation/mcp-server

"No templates found" Error

  • Create some templates in the Templation web app first
  • Make sure you're signed in with the same account

Connection Issues

  • Verify the TEMPLATION_API_URL is set correctly
  • Check your internet connection
  • Try creating a new API key

๐Ÿงช Testing Locally

You can test the MCP server locally:

# Test tool listing
echo '{"jsonrpc": "2.0", "id": 1, "method": "tools/list", "params": {}}' | \
  TEMPLATION_API_KEY=your_key_here npx @templation/mcp-server

# Test user info (replace with your actual API key)
echo '{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "get_user_info", "arguments": {}}}' | \
  TEMPLATION_API_KEY=your_key_here npx @templation/mcp-server

๐Ÿ“ Development

# Run in development mode
npm run dev

# Build for production
npm run build

# Start built version
npm start

๐Ÿ†˜ Support

If you need help:

  1. Check the troubleshooting section above
  2. Create an issue on GitHub
  3. Make sure your API key is valid and active