What is the key difference between DevTime and Stellavault?

DevTime belongs to the Knowledge & Memory category with local stdio execution, while Stellavault belongs to the Knowledge & Memory category with local stdio execution.

How do I install DevTime or Stellavault in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are DevTime and Stellavault free or paid?

DevTime operates under a Free / Open Source model (No auth required). Stellavault operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

DevTime lists 0 tools with 0 views and 0 GitHub stars. Stellavault lists 0 tools with 0 views and 3 GitHub stars.

Can I use both DevTime and Stellavault together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

How do I install DevTime or Stellavault in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are DevTime and Stellavault free to use, or do they require API keys?

DevTime is listed under a Free / Open Source model with No auth required . Stellavault operates under a Free / Open Source model with No auth required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both DevTime and Stellavault at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both devtime and stellavault as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, DevTime has a Quality Score of 27 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars. Stellavault holds a Quality Score of 39 /100 ( Fair ) with 0 views, 0 installs, and 3 GitHub stars.

Side-by-Side Model Context Protocol Comparison

DevTime vs Stellavault

In-depth architectural comparison of the DevTime and Stellavault MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

DevTime

Knowledge & Memory · Local stdio

Quality: 27/100 (Emerging) | Auth: No auth required

Stellavault

Knowledge & Memory · Local stdio

Quality: 39/100 (Fair) | Auth: No auth required

Verdict Summary: Choose DevTime if you need specialized Knowledge & Memory tools running via a local process. Choose Stellavault if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose DevTime when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore DevTime Details

Choose Stellavault when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Stellavault Details

Feature & Specification Comparison

Specification	D DevTime Knowledge & Memory	S Stellavault Knowledge & Memory
Summary	Local-first, read-only MCP server for evidence-backed repository memory.	Local-first MCP server: Claude searches, asks & drafts from your Obsidian vault. 21 tools, no keys.
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

Tools & Capabilities Breakdown

DevTime Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Stellavault Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

DevTime Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "devtime": {
      "command": "npx",
      "args": [
        "-y",
        "devtime"
      ]
    }
  }
}

Stellavault Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "stellavault": {
      "command": "npx",
      "args": [
        "-y",
        "stellavault"
      ]
    }
  }
}

Frequently Asked Questions

DevTime is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Stellavault belongs to Knowledge & Memory using local stdio subprocess. Select DevTime when you need capabilities focused on knowledge & memory and Stellavault when you require tools for knowledge & memory.

More alternatives to DevTime More alternatives to Stellavault Knowledge & Memory category hub