Issues, wiki, documents, and attachments — connected in one searchable knowledge graph, for your team and your AI agents.
A full tracker, a versioned wiki, hybrid search, and flexible metadata — one connected workspace for your team and your agents.
A full issue tracker — types, statuses, priorities, assignees, subtasks, and dependencies between issues. Plan with sprints, see the whole release on a roadmap, and switch between list and board views.
A versioned Markdown wiki with full history and one-click revert, page hierarchy, and cross-links straight to issues. Knowledge that outlives the people who wrote it.
Keyword and semantic search together, across issues, wiki, comments, and attachments. It finds work by meaning, not just exact words — search “login flow” and it surfaces the page that says “auth sequence.”
Typed metadata schemas that hold whatever your team needs — story points, git branches, severity, content status — defined per project or per issue type. More flexible than rigid custom fields, without the bolt-on feel.
Here's why teams move their work into Specivo.
Runs on your servers, even fully air-gapped. Nothing leaves your network.
Add your whole team and your AI agents. You're not billed per user.
Inspect it, extend it, fork it. No lock-in and no black boxes.
A built-in MCP server lets Claude Code, Codex, and others work the same issues and wiki as your team — reading a single wiki section or updating one field instead of the whole page. Fewer tokens, and every action is audited.
Tracker, wiki, search, and docs in one place — instead of stitching Asana, Confluence, and a search add-on together.
Issues, wiki, comments, and attachments link together — and all of it is found by one hybrid search.
Most tools are built for humans. Some are built for AI. Specivo is built for both.
AI agents read the same wiki, update the same issues, search the same knowledge base. Every action is tracked — who did what, human or AI, with full context. When you need to know what happened, you don't ask. You search.
ACME-5 Automate weekly compliance report
…compiling the weekly compliance report by hand every Monday.
Compliance Reporting
Quarterly compliance reports covering waste tonnage by material category.
compliance-report-q4-2025.pdf
Q4 2025 tonnage by material category for the district filing.
Alex on ACME-5
The scale CSV has a DISPOSITION column for landfill vs recycling.
Specivo ships with a built-in MCP server. Tested with Claude Code and Codex. Works with any tool that supports the MCP protocol.
One config line, and the agent stops guessing and starts looking things up.
// Add to your AI tool's MCP config: { "mcpServers": { "specivo": { "url": "http://localhost:8000/mcp", "apiKey": "spv_your_key_here" } } }
Specivo works perfectly without AI. When you're ready, enable it with one toggle—using a free local model or your own API key. Your choice.
No per-seat pricing. No user limits. Your team of 3 or 3,000 — same cost: zero.
AGPL licensed. No cloud dependencies. Your infrastructure, your rules.
Open-source tools we build alongside the platform.
A lightweight, extensible SEO metadata layer for Django — titles, meta tags, canonical URLs, hreflang alternates, JSON-LD schema, and Open Graph/Twitter cards across models and views, plus a versioned robots.txt. One consistent API, no extra dependencies.
