Perplexity + Specky
Connect Specky to Perplexity with a Custom MCP Connector
Where Perplexity’s custom remote connector surface is available, add Specky at https://www.specky.space/api/mcp and authorize the workspace with OAuth. Perplexity connector availability and any public directory placement depend on the account and product surface.
Canonical MCP endpoint
https://www.specky.space/api/mcpStreamable HTTP · OAuth 2.1 with PKCE · workspace key fallback
Setup
Connect Perplexity to Specky
Follow the provider-specific path below. The exact menu names and availability can change as each provider evolves its MCP and directory programs.
- 01
Open custom connectors
In the Perplexity product surface available to your account, choose the option to add a custom remote connector or MCP server.
- 02
Enter the Specky endpoint
Use https://www.specky.space/api/mcp and allow the client to discover the server capabilities and OAuth metadata.
- 03
Start with research and evidence
Use the connector to find product evidence, compare signals, and draft a cited brief. Keep workspace-changing tools out of the first test.
- 04
Treat listing availability as separate
A private connector does not imply a Perplexity marketplace listing. If the account exposes a partner or directory process, submit through that process with the same security and support links.
What to test first
Use one bounded, read-first prompt so you can inspect the returned evidence and confirm the workspace boundary:
Find the strongest evidence behind this customer problem, show the sources and unknowns, and draft a problem statement. Do not create tickets or change records until I approve the draft.
Questions about Specky and Perplexity
Is there a Perplexity marketplace submission for every MCP server?+
No public universal submission path is guaranteed. Perplexity supports custom connectors on some product surfaces, while directory or partner availability depends on the account and current product program.
What is a good first Perplexity plus Specky prompt?+
Ask for the strongest evidence behind a product problem, the sources that support it, the unknowns, and a small next experiment. This tests retrieval without immediately changing workspace state.
Does Perplexity get access to every Specky workspace?+
No. OAuth authorization is workspace-scoped. Connect only the workspace intended for the research session and remove the connector when it is no longer needed.