@osynhq/mcp-server

Osyn MCP (Model Context Protocol) Server - Local wrapper for Cursor and Windsurf AI editors.

Overview

This package provides a local MCP server that connects your AI editor (Cursor, Windsurf) to the Osyn platform, enabling access to your agreements and organizational data directly from your editor.

Features

- Seamless Integration: Automatically detected by Cursor and Windsurf
- Secure Authentication: Token-based authentication with Osyn
- Real-time Access: Direct access to your Osyn agreements and data
- Easy Setup: One-command initialization

Installation

No installation required! Use npx to run directly:

``bash
npx -y @osynhq/mcp-server init --token YOUR_TOKEN
`

Quick Start

$3

1. Go to your Osyn dashboard
2. Navigate to Settings → Integrations → MCP
3. Generate a new MCP token
4. Copy the token

$3

Run the init command with your token:

`bash
npx -y @osynhq/mcp-server init --token YOUR_TOKEN
`

This will automatically configure Cursor to use the Osyn MCP server.

$3

Close and reopen Cursor. The Osyn MCP server will start automatically.

Manual Usage

If you prefer to run the server manually:

`bash
npx -y @osynhq/mcp-server serve --token YOUR_TOKEN
`

Available Commands

$3

Configure Cursor to use Osyn MCP:

`bash
npx -y @osynhq/mcp-server init --token YOUR_TOKEN
`

$3

Start the MCP server (usually called automatically by Cursor):

`bash
npx -y @osynhq/mcp-server serve --token YOUR_TOKEN
`

$3

Test your connection to Osyn:

`bash
npx -y @osynhq/mcp-server test --token YOUR_TOKEN
`

Available Tools

Once configured, the following tools are available in your AI editor:

- get_agreements: Fetch all your agreements
- get_agreement_by_id: Get a specific agreement by ID
- search_agreements: Search agreements by keyword

Configuration

The MCP server configuration is stored in ~/.cursor/mcp.json.

Example configuration:

`json
{
"mcpServers": {
"osyn": {
"command": "npx",
"args": [
"-y",
"@osynhq/mcp-server",
"serve",
"--token",
"YOUR_TOKEN"
]
}
}
}
`

Environment Variables

- OSYN_SUPABASE_URL: Override the Osyn backend URL (advanced usage)

Troubleshooting

$3

1. Make sure you've run the init command
2. Restart Cursor completely
3. Check that ~/.cursor/mcp.json exists and contains the Osyn configuration

$3

Run the test command to verify your token:

`bash
npx -y @osynhq/mcp-server test --token YOUR_TOKEN
``

$3

- Make sure your token is valid and hasn't expired
- Generate a new token in the Osyn dashboard if needed

Support

For issues and support:
- Email: support@osyn.io
- Documentation: https://docs.osyn.io
- GitHub: https://github.com/osynhq/mcp-server

License

MIT