Cosense MCP Server

Related Servers

Alternatives to Cosense MCP Server

No user-submitted related servers found.

Related Servers

cosense-mcp-server
App Automation Developer Tools Code Execution
yosider
A
license
A
quality
C
maintenance
The cosense-mcp-server facilitates the integration with Claude Desktop by serving as a middleware command pipeline server, allowing for interaction with projects in cosense.
Updated 9 months ago (2025-12-22 07:02 UTC)
4
19 npm
23
MIT
headlo-mcpofficial
Content Management Systems Knowledge & Memory
headlohq
A
license
C
quality
D
maintenance
MCP server that provides Claude Desktop and Claude Code with access to Headlo collections, records, pages, components, and CAP sessions.
Updated 4 months ago (2026-06-15 04:14 UTC)
25
18 npm
Elastic 2.0
claude-agent-mcp
AI & Machine Learning Coding Agents Agent Orchestration
j-token
A
license
Not graded
quality
D
maintenance
An MCP server that wraps the Claude Agent SDK, enabling Claude-powered queries, coding tasks, web search, and customizable agent execution using OAuth without an API key.
Updated 6 months ago (2026-03-26 16:42 UTC)
38 npm
MIT
Personal Memory MCP Server
Knowledge & Memory Note Taking
Joopsnijder
A
license
Not graded
quality
D
maintenance
A modern MCP server that provides Claude Desktop with the ability to store and retrieve personal information locally.
Updated a year ago (2025-08-06 15:45 UTC)
1
MIT
Claude Memory
Knowledge & Memory Developer Tools
AmmarJawad
A
license
Not graded
quality
D
maintenance
An MCP server that provides Claude Code with persistent memory across sessions, including session checkpoints, image persistence, and bidirectional sync with claude.ai projects.
Updated 6 months ago (2026-03-25 16:48 UTC)
1
MIT
cc-session-search
Developer Tools Search
bwads001
F
license
B
quality
D
maintenance
An MCP server that provides tools for searching and analyzing Claude Code conversation history.
Updated a year ago (2025-09-20 23:15 UTC)
8
4
-

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.1/5.0

Scored 2026-04-18 11:30 across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: 'get_page' retrieves a specific page with its content and links, while 'list_pages' enumerates all known pages. There is no overlap or ambiguity between them, as one is for detailed retrieval and the other for listing.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern with snake_case: 'get_page' and 'list_pages'. The naming is predictable and readable, with no deviations or mixed conventions, making it easy to understand their functions at a glance.

Tool Count2/5

With only 2 tools, the server feels too thin for its apparent domain of managing pages in a project. It lacks essential operations like creating, updating, or deleting pages, which are typical for such a domain, making it under-scoped and limiting for agents.

Completeness2/5

The tool surface is severely incomplete for page management. While it provides read operations (get and list), it misses critical CRUD functions such as create, update, and delete, as well as other potential operations like searching or managing links. This will likely cause agent failures in handling full page lifecycles.