How to build your Aptora profile from your AI assistant
Filling in a profile is the least interesting part of looking for work. You have already written the content — it is in your old CV, in a LinkedIn export, in the notes from your last application. Retyping it into someone else’s form adds nothing.
Aptora speaks MCP, so an AI assistant you already use can do that part for you. The recording above is the whole flow, start to finish — three minutes, and spoken and shown in German, so the walkthrough below is here for everyone else.
What you are watching
The assistant is connected to Aptora and then asked, in plain English, to build a profile from an existing CV. Four things happen, and it is worth separating them because only the last one changes anything:
- It asks Aptora what a profile is. Aptora hands back the schema — sections, fields, allowed values — instead of the assistant guessing at a shape and producing something that has to be corrected later.
- It drafts. The content comes from the document you gave it. This is the part that would otherwise be twenty minutes of copying.
- It checks the draft against the schema before saving. A draft that would not be accepted is rejected here, while it is still a draft.
- It saves — as a draft. This is the first step that touches your account,
the first one your assistant asks you to confirm, and what lands is a draft:
in the recording the reply ends with a profile id and
Status: Entwurf. Nothing is public until you say so.
That order is deliberate on our side. Read, draft, validate, then write — so that the only irreversible step is the one you approve.
Connecting it yourself
The server address is /mcp on your Aptora host, and every client that speaks
MCP can use it. Setup differs per client — Claude, Cursor and the rest each
have their own dialog — so rather than repeat instructions that would quietly
go stale here, the current steps for each one live on the setup page:
Setup guide: connecting an AI assistant to Aptora
That page also lists, generated straight from the server, exactly which operations exist and what each permission covers. Worth two minutes before you grant anything.
What this does not do
Two limits are worth stating plainly, because “AI writes your profile” invites the wrong expectation:
- It does not invent experience. The assistant works from what you give it. If a role is missing from the document, it will be missing from the profile.
- It does not apply for you by accident. Applying is a separate, explicit operation with its own permission, and your client asks before it runs.
A profile drafted this way is a starting point, not a finished one — which is exactly why it arrives as a draft. Read it before you publish it: the assistant got the structure right so that you can spend your attention on the wording.
