Write the problem hypothesis
For [team], moving data between [system A] and [system B] requires [manual work], causing [delay or errors].
You can name one user, one situation and one measurable consequence without proposing a feature.Support Perplexity custom connectors (MCP Streamable HTTP) — POST /api/mcp rejects valid API keys with 401 / clients see HTTP 419
Evidence observed in pascalorg/editor, a Agent Infrastructure project.
12 comments0 positive reactions130 days openProject Radar 97
bug
Start free validation sprint4 guided steps · private notes · cloud sync
SOURCE EVIDENCE
Read original GitHub Issue ↗Start with what users actually said
Reporter context: What happened? Attempting to add Pascal as a custom MCP connector in Perplexity fails with: Investigation shows Pascal's endpoint accepts the API key on (returns the service descriptor with HTTP 200) but rejects the same key on the handshake that Perplexity actually performs, returning: The 419 surfaced in Perplexity…Excerpted from the public Issue. Read the complete thread before interpreting it.
Interview five affected users
- Which systems must exchange data?
- What triggers the handoff?
- Which fields or permissions block it?
- How is it handled today?
- Who owns failures between systems?
Run the smallest experiment
Manually operate or prototype one high-frequency connection for one team before building a general connector.
A user completes the real cross-system workflow twice and asks to keep the connection active.Make a build decision
- Build: repeated pain and active commitment
- Narrow: pain is real but the audience or job differs
- Stop: weak frequency or no behavioral proof
Why this brief exists
Information has value only when it changes action. This page turns one public signal into a bounded validation exercise. It is a research aid, not proof of demand, investment advice or a product recommendation.