Repository navigation
feat(mcp): add SpecStream as an MCP vendor - #265
Open
Specstreamai wants to merge 2 commits into
Open
Specstreamai wants to merge 2 commits into
Specstreamai wants to merge 2 commits into
Conversation
|
@Specstreamai is attempting to deploy a commit to the Comp AI - PoC Team on Vercel. A member of the Team first needs to authorize it. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I make SpecStream, the live web data engine, and this PR adds it as an MCP vendor. Today the agent researches one company or person at a time through Context.dev and Perplexity. SpecStream builds a whole dataset from the live web in one request and keeps it current, so the agent gets every matching company or person at once, with the source URL and read time on every value. The reasoning is in the ADR in the first commit,
adrs/specstream-mcp-vendor.md. The second commit is the code.The diff
packages/mcp-integrations/src/vendors/specstream.ts, new, same shape as Linear and Notionvendors/index.ts, one in the slug list intest/catalog.spec.ts, and one added testdocs/connections.mdRead-only access asks for
specs:read,finds:read,projects:readandaccount:read. Read-write addsspecs:write,finds:writeandfinds:spend.riskyToolslists the tools that spend or send:authorize_capacity_work,quote_capacity_work, schedules, destination syncs, share and export.I didn't add a logo, so the initials fallback in EntityLogo/ProviderMark applies.
docs/connections.mdcalls that the correct behaviour.Checks (Linux server,
oven/bun:1.4)bun run check-typesin packages/mcp-integrations: cleanbunx biome check packages/mcp-integrations: clean after formatbun testin the package: 13 pass, 0 failbun run lint:slopon the repo: 0 warnings, 0 errorsMcpOAuthClient.discoveragainst the live SpecStream endpoints: passes (issuer https://specstream.ai, registration endpoint present, S256)Not run: the apps/api and apps/agent integration tests, which need the Postgres from docker compose, and the full turbo pipeline.
MCP docs: https://specstream.ai/docs/mcp?utm_source=crm