Bespree Resumes
com.bespreePublished by bespree.comOfficial publisherv1.0.0Updated Oct 24, 2026
Create and edit saved resumes, make tailored or translated copies, and export PDF or Word.
Overview
Lets an assistant create and edit saved resumes, produce tailored or translated copies, and export them as PDF or Word files.
- What you can do
- This remote server connects an assistant to a Bespree account for resume work. According to the registry description, it can create and edit saved resumes, make tailored or translated copies of them, and export the results as PDF or Word documents. The manifest does not list individual tool names, so the exact operations are not enumerated.
- When to use it
- Use it when a user wants an assistant to draft, revise, or adapt resumes held in their Bespree account, for example producing a version tailored to a specific job posting or a translated copy, and then exporting it as PDF or Word. It is not intended for general document editing outside resumes.
- Requirements
- A remote MCP endpoint at using streamable HTTP. OAuth authentication is required, so the user needs a Bespree account and must complete an authorization flow. No environment variables, headers, or local packages are declared. Network access to the provider is needed.
Installation
In SourceWeft
- Open Bespree Resumes in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.bespree%2Fresumes/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"bespree-resumes": {
"type": "http",
"url": "https://bespree.com/api/v1/resume/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.