Dev Companion
by TYPO3
A local MCP server (plain PHP) that gives MCP-enabled clients a curated TYPO3 knowledge base, for the three audiences that work with TYPO3: the core contributor, the extension author, and the site developer.
No known CVEs
MIT license
Actively maintained
Last commit 6d ago
Works with most clients
Transport: stdio
2 tools · ~64 tok
Grade A · 0.0% of 200K ctx
MCPpedia last refreshed this data
Dev Companion is an MCP server that a local MCP server (plain PHP) that gives MCP-enabled clients a curated TYPO3 knowledge base, for the three audiences that work with TYPO3: the core contributor, the extension author, and the site developer. Its tool list has not been published yet over stdio, requires no API key, and scores 74/100 on MCPpedia's security, maintenance and efficiency rubric.
Step 1
Install in your client
Config is the same across clients - only the file and path differ.
CD
Supported in Claude Desktopstdio · Node 18+
Paste into ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"dev-companion": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Embed in your READMEAbout badges →
[](https://mcppedia.org/s/dev-companion)
Read me
What Dev Companion does
Experimental. This is a 0.x package and its surface is not settled. The > package name, the binary, the namespace and the environment variables all > changed in one cut on 2026-08-06. The tool names and the shapes they answer in > can move the same way. Pin a commit where you depend on it.
Test This Server
No automated test available for this server. Check the GitHub README for setup instructions.
Scored, not listed
Why this score
Five weighted categories - click any category to see the underlying evidence.
Score breakdown
74/100across 5 weighted dimensions
0255075100
16
13
20
15
10
−26
Security
Maintenance
Efficiency
Documentation
Compatibility
Categoriesclick a row to see evidence
Security
OSV.devNo known CVEs.
No package registry to scan.
Inventory
Tools (2)
Click any tool to inspect its schema.
~64 tokens total
Community
Reviews
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
How easy was setup?Did it work reliably?How was the documentation?
Sign in to write a review.
Frequently Asked Questions
- Is Dev Companion safe to use?
- Dev Companion has no known CVEs as of the latest MCPpedia security scan. Authentication requirements were not detected automatically - check the project's documentation before connecting in a shared environment. Licensed under MIT.
- How do I install Dev Companion?
- Dev Companion can be installed by cloning its GitHub repository and following the setup instructions in the README.
- What can Dev Companion do?
- Dev Companion provides 2 tools: Quickstart, Documentation. See the full tools list on the server page for descriptions and parameters.
- What AI clients work with Dev Companion?
- Dev Companion is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.
- Is Dev Companion actively maintained?
- Dev Companion is actively maintained - last commit was 6 days ago. It has 19 GitHub stars.
Related
Similar servers
Others in education / marketing
I
io.github.mims-harvard/tooluniverse962,700+ scientific tools for AI scientists: life science, research, literature, and more.
1.8k 4
Seo94Free Google Search Console MCP: your real GSC, Google Analytics and keyword data for AI agents.
588 2
I
io.github.amos689/paper-preflight93Checks every LaTeX reference against Crossref, dblp, arXiv, DataCite, PubMed and OpenAlex. No LLM.
95 5
I
io.github.retracn/ai-visibility92AI visibility for agents: is a brand mentioned and cited by Gemini, Claude and Google AI Overviews?
1
MCP Security Weekly
Get CVE alerts and security updates for Dev Companion and similar servers.
Community
Discussion
Start a conversation
Ask a question, share a tip, or report an issue.
Has anyone used this with Cursor?How do you handle auth?Any alternatives?
Sign in to join the discussion.