Hosted MCP server/Development

Persqo MCP server

Hosted at persqo.com·Streamable HTTP

Persqo is a remote HTTP server that uses API key authentication. AI personas browse a web app like real users, report usability bugs, and return copy-paste fix prompts for Claude Code and Cursor. An API key belongs to the workspace and can read or change every site on that account, so scope it carefully. A local stdio bridge is also published for clients that prefer it.

persqo.com Streamable HTTP API key Server not checked yet Reviewed 2026-11-04
About

Where it fits

Developers and product teams testing web app usability with AI personas and receiving fix prompts for Claude Code or Cursor.

  • Browse a web app with AI personas.
  • Report usability bugs found by personas.
  • Get copy-paste fix prompts for Claude Code or Cursor.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Local stdio server

Installed from GitHub, with PERSQO_API_KEY in the environment.

npx -y github:YaakovTzedek/persqo-mcp

Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.

Connection

Endpoint and configuration

Endpoint
https://persqo.com/api/mcp
Host
persqo.com · /api/mcp
Transport
Streamable HTTP
Authentication
API key
Server name
persqo
Listing type
Community or directory listing

The installer uses the server name persqo. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that persqo appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Browse a web app with AI personas. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider source

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Persqo repositoryhttps://github.com/YaakovTzedek/persqo-mcp