Blender integration through the Model Context Protocol
Nothing to run from here
CMeIn is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
10
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Turns ordinary phone photos of you into photos of you having a life. Advice, credits, 4,500 scenes.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http cmein-mcp https://mcp.cmein.com/mcp
# 2 — ask your agent for something these tools do
# photo_advice, cmein_pricing, see_examples and 7 more
CMeIn costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CMAll 1 server
cmein1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http cmein-mcp https://mcp.cmein.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Answers a question about dating-profile photos — what works, what does not, lighting, angles, backgrounds, expressions, what dating apps do with them — from CMeIn's published articles. Returns the relevant passages with a link to each source article, and the date the content was last synced. No account needed.
No parameter schema on file.
What CMeIn costs: the credit packs and their prices, how many credits one generated photo spends, and that there is no subscription. Read from the live pricing page at request time, so the figures are current. No account needed.
No parameter schema on file.
Where to see CMeIn's actual output: the examples gallery, organised by scene, plus the accounts where new work is posted, and how many scenes the product offers. Use this when someone wants to judge the results for themselves rather than read about them. No account needed.
No parameter schema on file.
Finds one of CMeIn's short films by what it is about. The films are dating scenarios — money and dating, who pays, why people run, what she actually said — and every character in them is generated by CMeIn, which is the point they are making. Returns titles, links and view counts. Covers the 15 most recent films only. No account needed.
No parameter schema on file.
Reads one of CMeIn's own information pages and returns its text with the link: "pricing" — what CMeIn costs — credit packs, the price of one photo, and that there is no subscription; "examples" — the gallery of generated photos, by scene, and whose photos they are; "faq" — how many reference photos are needed, whether results look like you, what happens to uploads, whether dating apps allow them;
No parameter schema on file.
Sends a message to CMeIn's support inbox and gets a reply by email. For questions the articles and pages do not answer, problems with an order, or anything that needs a person. Needs an email address to reply to. No account needed. This sends a real message to a real person — only call it when someone has asked to be put in touch, and show them the text first. For a refund of unspent credits, see
No parameter schema on file.
The credit balance on the signed-in CMeIn account, and roughly how many photos that buys. Needs the "credits:read" permission.
No parameter schema on file.
The most recent photos generated on this account — the scene each one was, whether it finished, and when. The images themselves stay in the app rather than passing through here. Needs the "photos:read" permission.
No parameter schema on file.
Searches CMeIn's scene catalogue — over 4,500 settings, filtered to the ones that suit this account. Use it to recommend one: describe what the person is after and it finds the scenes that fit. Generating the photo itself is done in the app. Needs the "scenes:read" permission.
No parameter schema on file.
Opens a request for credits to be returned when a generated photo did not look like the person. It goes to a human and is answered by email; the refund policy decides the outcome, not this tool. Needs the "support:write" permission.
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install CMeIn or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.1.
1.1.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish CMeIn can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.