Authentication

Authentication

Pulsar MCP Server uses bearer token authentication for beta access participants.

Getting Your Bearer Token

Free Beta Program

We're offering free limited betaaccess to the first batch of AI agent builders.

To request access:

Include in your request:

  • Brief description of your agent project

  • Expected usage volume (requests per day)

  • Integration timeline

  • Any specific channels you want monitored

Response time: Within 24 hours

Using Your Bearer Token

In MCP Client Configuration

Add the token to your MCP client headers:

For HTTP Transport (Claude Desktop, Windsurf, etc.):

{
  "mcpServers": {
    "pulsar": {
      "type": "http",
      "url": "https://mcp.askpulsar.com/mcp",
      "headers": {
        "Authorization": "Bearer your-token-here"
      }
    }
  }
}

For SSE Transport (ElizaOS, real-time frameworks):

{
  "mcpServers": {
    "pulsar": {
      "type": "sse",
      "url": "https://mcp.askpulsar.com/mcp/sse",
      "headers": {
        "Authorization": "Bearer your-token-here"
      }
    }
  }
}

That's It!

Once your MCP client is configured with the bearer token, it will automatically:

  • Discover all Pulsar tools

  • Handle authentication on every request

  • Manage the protocol communication

You just interact with your agent naturally:

  • "List all channels"

  • "Summarize Virtuals Protocol"

  • "Search for AI agent news"

The MCP client and server handle everything else.

Rate Limits

With Bearer Token:

  • ✅ 60 requests per minute (dedicated)

  • ✅ Burst allowance up to 100 requests

  • ✅ Not shared with other users

  • ✅ Production-ready

Without Token (Testing Only):

  • ⚠️ 60 requests per minute (shared across all anonymous users)

  • ⚠️ Subject to throttling during peak times

  • ⚠️ Not recommended for production agents

Security Best Practices

✅ Do This

Store in Environment Variables:

export PULSAR_TOKEN="your-token-here"

Use Secrets Manager:

import os
BEARER_TOKEN = os.getenv("PULSAR_TOKEN")

Rotate Periodically: Contact us if you need to rotate your token for security reasons.

❌ Don't Do This

  • ❌ Never commit tokens to git

  • ❌ Don't hardcode in source code

  • ❌ Don't share between projects

  • ❌ Don't expose in client-side code

Troubleshooting

Error: "Invalid bearer token"

Possible causes:

  • Token is incorrectly copied (extra spaces)

  • Wrong header format

  • Token has been revoked

Solution:

  1. Verify header format: Authorization: Bearer <token>

  2. Check for extra whitespace

  3. Contact us if issue persists

Error: "Rate limit exceeded"

Possible causes:

  • Making >60 requests per minute

  • Burst limit exceeded

Solution:

  1. Implement exponential backoff

  2. Add delays between requests

  3. Contact us if you need higher limits

Error: "Missing authorization header"

Possible causes:

  • Header not included in request

  • MCP client config incorrect

Solution:

  1. Verify header is set in config

  2. Check MCP client syntax

  3. See examples above

Token Management

Getting a New Token

If you lose your token or need to rotate it:

  • Email [email protected]

  • Include your original request details

  • New token provided within 24 hours

Revoking Access

To revoke your token:

Beta Program Details

What's Included:

  • Free MCP server access

  • Dedicated rate limits (60 req/min)

  • 1:1 integration support

  • Early influence over features

  • Lifetime discounted pricing (after beta)

Duration:

  • Free while in beta

  • We'll notify before any pricing changes

  • Beta participants get special pricing

Limitations:

  • Limited to first 10 builders

  • Subject to fair use policy

  • Must be for legitimate agent development

Need Help?

Get Support:

Request Features:

  • Need specific channels monitored?

  • Want custom rate limits?

  • Have integration questions?

We're here to help you succeed!

PreviousAboutNextExamples

Last updated