Contribute to SERPHouse
Help build SERPHouse in the open: SDKs, agent harnesses, docs, and tooling. Start at github.com/SERPHouse.
SERPHouse is built in the open. Whether you improve an official SDK, write an agent harness guide, fix docs, or ship tooling around the SERP API → contributions are welcome.
Build the SERP stack with us
SERPHouse is built in the open. Fix a bug, ship an SDK feature, write a guide, or plug us into a new agent harness — every contribution makes search data easier for developers worldwide.
github.com/SERPHouse
SDKs & Libraries
Ship bug fixes, features, and new language ports for the official clients.
Agent Harnesses
Document how SERPHouse plugs into Claude Code, Cursor, Codex, and more.
Documentation
Improve guides, fix typos, and add clearer examples for every API.
Ideas & Integrations
Tutorials, example apps, plugins, and translations all count.
Where to contribute
Everything lives under the SERPHouse GitHub organization. Pick a repo, open an issue, or send a pull request.
Official open-source repos
| Project | What you'll work on | Repository |
|---|---|---|
| Node.js SDK | Client API, types, examples | SERPHouse/serphouse-nodejs |
| PHP SDK | Client API, packaging, docs | SERPHouse/serphouse-php |
| MCP Server | Tools, config, agent integrations | SERPHouse/serphouse-mcp |
| Agent Skills | Skill docs for AI coding agents | SERPHouse/agent-skills |
| AI SDK (Python) | LangChain / LlamaIndex tooling | SERPHouse/ai-sdk-python |
| n8n Node | No-code workflows with SERPHouse | SERPHouse/n8n-node-serphouse |
New to open source?
Small PRs are perfect first contributions: typo fixes, clearer examples, and missing parameter notes all help.
Ways you can help
SDKs & libraries
Bug fixes, new language ports, better error messages, and feature additions are all appreciated. Prefer PRs that include tests and a short note on why the change matters.
Agent harnesses
Integrations live in content/docs/agent-harnesses/. If you've wired SERPHouse into Claude Code, Cursor, Codex CLI, OpenCode, VS Code, Smithery, or another agent → document it using the existing page pattern.
Documentation
This site is MDX under content/docs/. Clearer copy, better tables, and runnable examples make the product easier for everyone.
More ideas
- Example projects: dashboards, research tools, SEO workflows
- Tutorials: competitor analysis, local SEO tracking, news monitoring
- Integrations: WordPress, Shopify, or other platforms
- Translations: docs in more languages
How to contribute docs
Fork the org
Start from github.com/SERPHouse and fork the docs (or the relevant product) repository.
Edit or add a page
Add or update MDX under content/docs/. Match the tone and structure of nearby pages.
Update navigation
If you add a new page, register it in content/docs/meta.json (or the section meta.json) so it appears in the sidebar.
Open a pull request
Describe the change, link related issues, and call out anything reviewers should verify.
Guidelines
Keep it consistent
Follow existing MDX patterns: frontmatter, Callouts, Cards, tables, and resource links.
- Keep examples concise and runnable
- Test API examples before submitting
- For SDK changes, include tests with your PR
- Prefer clear language over jargon → readers should get value in under a minute
- Never commit API keys or secrets
Ready when you are
Jump into the org, star a repo you care about, and open your first PR. The community (and future you) will thank you.
Related Links
Last updated on
How is this guide?