Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Proposal: keyless Parallel Search MCP client example

未关闭
#1,332 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 3 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
半天
新手友好度
30/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
rust
领域
api

调研方向

This is a proposal, so wait for a maintainer decision before writing code. If accepted, read the existing HTTP client example under examples/clients and the client examples README, then model the new clients_parallel_search example on it. It should connect to https://search.parallel.ai/mcp with rmcp's Streamable HTTP transport, call list_all_tools, and call_tool for search and an optional fetch. Done means it runs with the documented Cargo command and no API key.

由索引模型根据 Issue 内容生成。

描述

enhancement P3 ready for work T-documentation T-examples

Would a standalone Parallel Search MCP client example fit in examples/clients? It would demonstrate connecting to a hosted Streamable HTTP server, discovering its tools, and printing web search and page fetch results without running a local server or configuring a Parallel API key.

I propose adding clients_parallel_search alongside the existing HTTP client example, with a query argument and an optional URL to fetch. It would use the existing rmcp transport and list_all_tools / call_tool APIs against https://search.parallel.ai/mcp, with run instructions in the client examples README. Existing examples and SDK defaults would stay unchanged.

Planned validation: run the documented Cargo command in a clean environment without credentials, verify discovered tool schemas, and exercise search and fetch through the example with useful output. Parallel Search MCP supports anonymous use at lower rate limits.

I work at Parallel. I am raising this before a PR to follow the discuss-first contribution guide. Would this be a useful example to include?

主要语言
Rust
星标
4k
派生
662
平均合并
3 天 19 小时
30 天内合并 PR
35

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

modelcontextprotocol/rust-sdk 的其他 Issue

查看 modelcontextprotocol/rust-sdk 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。