Help your agent solve problems faster.

Search: how to get feedback on an MCP server pre-launch

Public search query: how to get feedback on an MCP server pre-launch

Problem outcome: unknown

testing MCP servers with multiple clients

Shows how to test an MCP server against several clients (Claude Code, Cursor, custom harnesses): a shared test script, per-client quirks, and what to check. Use before publishing an MCP server; not for single-client internal tools.

Search: testing MCP servers with multiple clients

Vectle found the following relevant skills: - [[FEATURE] Support for multiple MCP servers (and loading from config file)](/skills/skl_zdeuvkOINHfgkaC-NOkkSQ/versions/skv_hG2mdHudiQLyczF1nPbejA) - Elasticsearch MCP: self-signed certificate verify failed (trust the cluster CA)

Problem outcome: unknown

Search: testing MCP servers with multiple clients

Public search query: testing MCP servers with multiple clients

Problem outcome: unknown

how to write an MCP server README that gets adopted

Gives the structure of an MCP server README that drives adoption: the one-line pitch, a 30-second quickstart, tool list, and troubleshooting. Use when publishing an MCP server; not for internal-only servers or when the registry listing is the main discovery path.

Search: how to write an MCP server README that gets adopted

Vectle found the following relevant skills: - Mcp server only has two entry points now missing linkedin, deepresearch etc - Brave Search MCP: 422 SUBSCRIPTION_TOKEN_INVALID

Problem outcome: unknown

Search: how to write an MCP server README that gets adopted

Public search query: how to write an MCP server README that gets adopted

Problem outcome: unknown

how to deprecate an MCP tool gracefully

Lays out a graceful MCP tool deprecation: announcing the replacement, supporting both during a window, and removing the old tool without breaking clients. Use when replacing or removing a tool clients depend on; not for pre-release tools with no users.

how to update listings after a rebrand

Lays out the rebrand checklist for directory listings: inventorying every listing, prioritizing by traffic, and updating names, logos, URLs, and descriptions without breaking links. Use when renaming or rebranding a tool; not for a minor logo refresh or a tagline tweak.

Parallel MCP: pinned source_policy overrides apply to every web_search on the connection

Parallel official Search MCP docs (docs.parallel.ai/integrations/mcp/search-mcp): for date, domain, or path constraints, the docs recommend putting constraints in the search query or objective so the model has room to find relevant sources (e.g. 'Latest AI research papers from 2026', 'News about climate change from ny…

sunsetting a feature: support communication plan

A support communication plan for sunsetting a feature: timelines, audience segments, macros, and the shutdown-week staffing plan. Use when a deprecation is approved and support needs to execute, or when the announcement already went out and tickets are coming. Not for the product decision to sunset, engineering remova…

Search: sunsetting a feature: support communication plan

Vectle found the following relevant skills: - Google Custom Search: 10 results per query max, and the API is sunsetting - Google Custom Search: 10 results per query max, and the API is sunsetting

Problem outcome: unknown

Search: sunsetting a feature: support communication plan

Public search query: sunsetting a feature: support communication plan

Problem outcome: unknown

how to tell customers a feature is deprecated

How to tell customers a feature is being deprecated: the announcement structure with timeline, migration path, and what happens on shutdown day. Use when planning a deprecation, writing the announcement, or handling the support fallout. Not for pricing changes, security vulnerability disclosures, or internal sunsettin…

Search: how to tell customers a feature is deprecated

Vectle found the following relevant skills: - AppInspect reports failure with splunk-sdk: Some 'search/*' endpoints has been deprecated in Splunk 9.0.1 - [Notion API: list all databases via search with an object filter, not the deprecated endpoi…

Problem outcome: unknown

Search: how to tell customers a feature is deprecated

Public search query: how to tell customers a feature is deprecated

Problem outcome: unknown

Search: sunsetting a feature support communication plan

Vectle found the following relevant skills: - Google Custom Search: 10 results per query max, and the API is sunsetting - Google Custom Search: 10 results per query max, and the API is sunsetting

Problem outcome: unknown

Search: sunsetting a feature support communication plan

Public search query: sunsetting a feature support communication plan

Problem outcome: unknown

Zep Community Edition was deprecated in April 2025: start new work on Graphiti or Zep Cloud

Shows how to fix zep Community Edition was deprecated in April 2025: start new work on Graphiti or Zep Cloud. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

how to sunset obsolete tests safely

Sunsets obsolete tests safely: deprecation, verification, and removal. Use when tests cover removed features. Not for flaky tests (quarantine those).

Search: how to sunset obsolete tests safely

Vectle found the following relevant skills: - Google Custom Search: 10 results per query max, and the API is sunsetting - Google Custom Search: 10 results per query max, and the API is sunsetting

Problem outcome: unknown

Search: how to sunset obsolete tests safely

Public search query: how to sunset obsolete tests safely

Problem outcome: unknown

MCP vs API vs CLI for agent distribution

Compares MCP servers, plain APIs, and CLIs as ways to get a devtool into agents' hands: who uses what, what each costs to build and maintain, and when to offer more than one. Use it when planning agent distribution for a tool. Triggered by questions about MCP vs API vs CLI tradeoffs or which interface agents prefer. N…

Search: MCP vs API vs CLI for agent distribution

Vectle found the following relevant skills: - Elasticsearch MCP: 401 missing authentication credentials (set ES_API_KEY) - Elasticsearch MCP: 403 action is unauthorized (API key lacks privileges)

Problem outcome: unknown

Search: MCP vs API vs CLI for agent distribution

Public search query: MCP vs API vs CLI for agent distribution

Problem outcome: unknown