-
Notifications
You must be signed in to change notification settings - Fork 0
update #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update #1
Conversation
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
Adding KRS Poland MCP Server
…rver Add Customer.io integration to README
Add PinMeTo MCP server entry to README
Added SendGrid MCP link to the README
add official sql server
Add TextArtTools MCP server
Added Unity-MCP to the Community Servers section
Add Kalendis to README
Add Bitnovo Pay MCP server to third-party integrations
Mixpanel MCP server info
Add Bauplan to MCP list
Add Kiln to integration list
Add Playwright Wizard MCP server
chore: add Chrome DevTools MCP to Official Integrations
…ng URIs, incl. data URIs)
add zip tool to everything server
* 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>
- 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
There was a problem hiding this 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 | |||
There was a problem hiding this comment.
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)
| if: | | ||
| always() && | ||
| needs.update-packages.outputs.changes_made == 'true' && | ||
| (needs.publish-pypi.result == 'success' || needs.publish-npm.result == 'success') |
There was a problem hiding this comment.
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.
Description
Server Details
Motivation and Context
How Has This Been Tested?
Breaking Changes
Types of changes
Checklist
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.
filesystem: New secure server with path validation, search (glob/filters), file edit (diff), tail/head, and utilities; TypeScript tests and Vitest setup.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 toMcpServer, adds structured outputs and tests.sequentialthinking: Refactored toMcpServer, extracted lib, Zod validation, structured outputs, tests.time: AddsLOCAL_TIMEZONEsupport, robust local TZ detection (tzlocal), includesday_of_week, Docker/env updates, tests.gdrive,github,gitlab,google-maps,postgres,puppeteer,redis,sentry,slack,sqlite(code, Dockerfiles, READMEs).filesystem,memory,sequentialthinking; expanded Python tests fortime.mcpName, repo), SDK bumped to^1.24.0.Written by Cursor Bugbot for commit 792c474. This will update automatically on new commits. Configure here.