Skip to content

Conversation

@t8or
Copy link
Owner

@t8or t8or commented Dec 15, 2025

Description

Server Details

  • Server:
  • Changes to:

Motivation and Context

How Has This Been Tested?

Breaking Changes

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Protocol Documentation
  • My changes follows MCP security best practices
  • I have updated the server's README accordingly
  • I have tested this with an LLM client
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have documented all environment variables and configuration options

Additional context


Note

Introduces a new secure filesystem server, significantly upgrades git, memory, sequential-thinking, and time servers (with tests and VS Code integration), and removes multiple deprecated servers.

  • Servers:
    • Added:
      • filesystem: New secure server with path validation, search (glob/filters), file edit (diff), tail/head, and utilities; TypeScript tests and Vitest setup.
    • Enhanced:
      • git: New options (diff context lines), date-filtered logs, branch listing tool; expanded tests; Dockerfile adds git-lfs; dependency updates.
      • memory: Migrates to JSONL storage with auto-migration, switches to McpServer, adds structured outputs and tests.
      • sequentialthinking: Refactored to McpServer, extracted lib, Zod validation, structured outputs, tests.
      • time: Adds LOCAL_TIMEZONE support, robust local TZ detection (tzlocal), includes day_of_week, Docker/env updates, tests.
    • Removed:
      • Deprecated servers: gdrive, github, gitlab, google-maps, postgres, puppeteer, redis, sentry, slack, sqlite (code, Dockerfiles, READMEs).
  • Tooling/Tests:
    • Added Vitest configs/tests for filesystem, memory, sequentialthinking; expanded Python tests for time.
  • Docs/Config:
    • README updates (VS Code/Docker install badges & instructions); package metadata (mcpName, repo), SDK bumped to ^1.24.0.

Written by Cursor Bugbot for commit 792c474. This will update automatically on new commits. Configure here.

olaservo and others added 30 commits October 7, 2025 07:12
Add MCPShell tool to README.md
Changed logo URL to official Chrome favicon and updated alt text to "Chrome".

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
Add YetiBrowser MCP to Community registry
Add ActivityPub MCP server to community servers list
Add Commerce Layer to official integrations list
docs: add CoinStats MCP server to official integrations in README
…rver

Add Customer.io integration to README
Add PinMeTo MCP server entry to README
Added SendGrid MCP link to the README
Add TextArtTools MCP server
Added Unity-MCP to the Community Servers section
Add Bitnovo Pay MCP server to third-party integrations
Add Kiln to integration list
chore: add Chrome DevTools MCP to Official Integrations
* Add Console Automation MCP server

Production-ready MCP server for AI-driven console automation and monitoring.
Features 40 tools for session management, SSH, testing, monitoring, and background jobs.
Like Playwright for terminal applications.

- Added to Third-Party Servers section (alphabetically positioned)
- GitHub: https://github.com/ooples/mcp-console-automation

* Remove duplicate Console Automation entry from README

Removed duplicate entry for Console Automation in the README.

---------

Co-authored-by: franklinic <franklin@ivorycloud.com>
* Update README.md

* Update README.md

---------

Co-authored-by: adam jones <domdomegg+git@gmail.com>
olaservo and others added 28 commits November 26, 2025 07:47
- Add .mcp.json with mcp-docs HTTP server configuration
- Update claude.yml to load MCP server config with --mcp-config
- Change --system-prompt to --append-system-prompt to preserve defaults
- Extend instructions to use mcp-docs for MCP-related work

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
* Add Uno Platform MCP

* Update logo and description
Add MCP docs server to Claude Code GitHub Action
* Add Atono MCP to the list

* Shorten the description
* Add AI Endurance MCP server to README: AI-powered training platform for endurance athletes with 20 tools including workout management, activity analysis, performance predictions, and recovery tracking. Supports cycling, running, and triathlon.

* Move AI Endurance to community servers
* add useless toolkit mcp servers

* change postion

move from community group to official group

* Move Toolkit from official group to community group

Move Toolkit from official group to community group
Bumps the npm_and_yarn group with 1 update in the / directory: [express](https://github.com/expressjs/express).


Updates `express` from 4.21.2 to 4.22.0
- [Release notes](https://github.com/expressjs/express/releases)
- [Changelog](https://github.com/expressjs/express/blob/4.22.0/History.md)
- [Commits](expressjs/express@4.21.2...4.22.0)

---
updated-dependencies:
- dependency-name: express
  dependency-version: 4.22.0
  dependency-type: direct:production
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <support@github.com>
…_yarn/npm_and_yarn-6c4b93b8de

chore(deps): bump express from 4.21.2 to 4.22.0 in the npm_and_yarn group across 1 directory
Bumps the npm_and_yarn group with 1 update in the / directory: [@modelcontextprotocol/sdk](https://github.com/modelcontextprotocol/typescript-sdk).


Updates `@modelcontextprotocol/sdk` from 1.23.0 to 1.24.0
- [Release notes](https://github.com/modelcontextprotocol/typescript-sdk/releases)
- [Commits](modelcontextprotocol/typescript-sdk@1.23.0...1.24.0)

---
updated-dependencies:
- dependency-name: "@modelcontextprotocol/sdk"
  dependency-version: 1.24.0
  dependency-type: direct:production
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <support@github.com>
…_yarn/npm_and_yarn-68057ba13a

chore(deps): bump @modelcontextprotocol/sdk from 1.23.0 to 1.24.0 in the npm_and_yarn group across 1 directory
* In everything.ts
  - In elcitiation request,
    - Update all fields to have a title property
    - Add all 5 enum types supported by the SDK
      - legacy titled single select
      - titled single select
      - titled multi select
      - untitled single select
      - untitled multi select
    - Use faux ids (e.g., hero-1, hero-2) for enum value when titled to illustrate the difference.
Remove .vscode settings and add them to .gitignore
Add mcp__mcp-docs and WebFetch to allowedTools so Claude can use
the MCP docs server and fetch schema content from GitHub URLs.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Cliff Hall <cliff@futurescale.com>
…h-name-in-tests

Fix test_git_diff to use dynamic branch name
…hema (#3113)

* fix(filesystem): return string in structuredContent to match outputSchema

The directory_tree, move_file, and list_directory_with_sizes tools were
returning an array in structuredContent.content, but outputSchema declares
content as z.string(). This caused MCP error -32602 validation failures.

Changed structuredContent from { content: [contentBlock] } to { content: text }
to match the declared outputSchema and be consistent with other filesystem
tools like list_directory and search_files.

Fixes #3110, #3106, #3093

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* test(filesystem): add integration tests for structuredContent schema compliance

Adds tests to verify that directory_tree, list_directory_with_sizes, and
move_file tools return structuredContent.content as a string (matching
outputSchema) rather than an array.

These tests prevent regression of issues #3110, #3106, #3093.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: adam jones <domdomegg+git@gmail.com>
Removed Openfort entry from the list of projects.
The public hosting for the Orkes logo changed, necessitating this update.
Co-authored-by: Ola Hungerford <olahungerford@gmail.com>
Co-authored-by: Ola Hungerford <olahungerford@gmail.com>
Update Everything server's elicitation request
@t8or t8or merged commit 090d4b0 into t8or:main Dec 15, 2025
1 check passed
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR is being reviewed by Cursor Bugbot

Details

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

@@ -45,6 +45,43 @@ jobs:
working-directory: src/${{ matrix.package }}
run: uv sync --frozen --all-extras --dev
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Inconsistent dependency sync flags between test and build jobs

The newly added test job uses uv sync --frozen while the build job was changed to use uv sync --locked. The --frozen flag installs from the lockfile without verifying it matches pyproject.toml, whereas --locked requires the lockfile to be up-to-date and fails if it's not. This inconsistency means tests could pass while the subsequent build step fails due to lockfile verification, or worse, tests could run with different dependencies than the build.

Additional Locations (1)

Fix in Cursor Fix in Web

if: |
always() &&
needs.update-packages.outputs.changes_made == 'true' &&
(needs.publish-pypi.result == 'success' || needs.publish-npm.result == 'success')
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Release created when publish jobs partially fail

The new create-release condition using always() with OR logic allows a release to be created even when one of the publish jobs fails. If publish-pypi succeeds but publish-npm fails (or vice versa), the GitHub release will still be created. However, the release notes artifact is generated early by create-metadata and includes all changed packages regardless of publish outcome. This means a release can be created that references packages that weren't actually published, potentially confusing users who try to install unavailable packages. The previous behavior without always() prevented releases when any publish dependency failed.

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.