Which Copilot surface supports this?

The custom MCP server path works in VS Code's Copilot Chat and in the Copilot CLI (copilot mcp add, with the config stored in your mcp-config.json). The consumer Copilot app uses built-in connectors and doesn't accept custom URLs today.

If I connect FamilySearch API to Copilot, can I use the same connection in Claude or ChatGPT later?

Yes, and that's the point: the connection is yours, not Copilot's. You paste the same link in any AI you use, and there's nothing new to set up or pay again. Connect a new AI and FamilySearch API is already there.

Do I need to hand my FamilySearch API password to Copilot?

Never. You sign in once at Vinkius, and we keep your logins encrypted and away from your AI. Copilot only ever sees the link, and you can remove it whenever you want.

What can I actually ask Copilot to do with FamilySearch API?

Whatever the Connector covers: check data, run actions and bring answers back into the session. The Connector page lists every capability your AI gains, with real examples you can copy.

Copilot doesn't show the Connector. What do I check?

Open the MCP list in your editor or run copilot mcp list, confirm the server was added with the link pasted exactly as copied, and confirm the Connector is active in your Vinkius account. A deactivated Connector stops responding.

Can I remove the access later?

Anytime. Remove the server from your MCP list (or your mcp-config.json) and it's out of your sessions. Your Vinkius account keeps the connection and its history either way, ready for the next AI.

How to give Microsoft Copilot access to FamilySearch API

Set up in seconds, once. From then on, Copilot gets things done for you: FamilySearch API becomes a custom MCP server in your Copilot, ready in every session.

Ask AI about this guide

FamilySearch API Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_NBvLpXdOI5ehLMBDuWXjBbjUwW8SLFHFZoz8epVV/mcp

Connecting FamilySearch API to Copilot

About a minute, in VS Code's Copilot Chat

1In VS Code, open the Copilot Chat panel, click the tools icon and select the + icon, or run MCP: Add Server from the Command Palette.
2Choose your scope, name the server, and paste your FamilySearch API link as the server URL with HTTP transport.
3Confirm the server appears in your MCP list, then ask Copilot something real. FamilySearch API is now part of your Copilot.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "familysearch-api-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_NBvLpXdOI5ehLMBDuWXjBbjUwW8SLFHFZoz8epVV/mcp"
    }
  }
}

Microsoft Copilot + FamilySearch API

One chat. Your FamilySearch API, live inside Microsoft Copilot.

Real prompts, answered with live data. This is the kind of conversation you will have in Copilot once the server is in.

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

These prompts ship with the FamilySearch API Connector. Once yours is connected, they work in your sessions.

The full capability set, the prompts and the observed latency live on the FamilySearch API Connector page.

Mission Control

See everything your Microsoft Copilot agents do in FamilySearch API.

When Copilot runs a tool in FamilySearch API, it happens on Copilot's side: you see the result, but not the request itself, what data it carried, or whether a rule was broken.

Now every move lands on your screen.

Every execution is recorded, enforced, and shown to you: what ran, what it returned, what was blocked, and why.

AI Briefing

Upgrade to unlock

Know exactly what needs your attention before you even look at the charts. One briefing. The full picture. The next move.

Requests

Total in this period

Avg Latency

API 88ms · Overhead 54ms

Vinkius Reliability

Agent 280 · Upstream 47 · Vinkius 15

Tokens

AI tokens processed

DLP Protected

Sensitive data redacted

Cost Saved

FinOps truncations applied

AI Agents Activities

last 30 days

30d agotoday

Request Volume & Latency

requests latency

Every request your Microsoft Copilot agents make through FamilySearch API is logged, enforced and auditable. See how AI Governance turns agent activity into accountability, and what it means for your FamilySearch API workflows.

What sets us apart

It's not just the Connector that stays safe. Everything your agents do through it is.

Connecting FamilySearch API to your AI is step one. But an open line between your agents and FamilySearch API is only half the story: without protection, every action they take runs unguarded.

That's why protection doesn't stop at the door.

Every action your agents take through the Connector runs inside our infrastructure: signed activity logs, automatic key rotation, spending limits that pause instead of surprise, and a sandbox that isolates every execution.

Tamper Proof Activity Log

Every request your agents make in FamilySearch API is recorded and signed, so any change to the history becomes detectable.

Automatic Key Rotation

We rotate security keys every 24 hours. Your FamilySearch API connection stays protected without any manual work.

Spending Protection

We enforce the spending limit you choose and pause actions that exceed it until approval is received. Your FamilySearch API actions never surprise you.

Isolated Sandbox

Every execution through FamilySearch API runs isolated, with 34+ security rules covering memory, CPU, network access, file handling and execution.

Security Event Streaming

Security events flow to Splunk, Datadog or your own webhook, so FamilySearch API activity lands in the tools you already rely on.

Instant Resume

Idle connections resume in 3 to 5 ms while preserving their state, keeping your Microsoft Copilot sessions responsive.

Malicious File Protection

We detect compressed files designed to exhaust system resources and block them before they ever reach FamilySearch API.

Credential Validation

We test your FamilySearch API credentials before saving them. Invalid credentials are rejected instead of being stored.

Separate Usage Limits

Usage stays isolated per account, so activity in one connection never consumes another account's allowance.

One Connector, one link, and the whole operation is protected. Not just the connection: everything your agents do through it.

These guarantees are not add-ons: they are the infrastructure every FamilySearch API connection runs on. Read how our infrastructure protects everything your Microsoft Copilot agents do, end to end.

Inside Vinkius

Get FamilySearch API ready for your AI. It's easy.

You choose FamilySearch API from the Vinkius Catalog, sign in to your FamilySearch API account, and get one connection link. That's it.

You choose FamilySearch API
You find FamilySearch API in the Catalog and install the Connector with one click.
FamilySearch API
Active
Enable Connector
Activating…
You sign in
You connect your FamilySearch API account and choose what you want your AI to access. Your credentials stay encrypted and separate from your AI.
Configure Credentials
Configure credentials for {{connectorName}}
FamilySearch API sign-inRequiredEncrypted
Save & Continue
Encrypted Storage
Your credentials are encrypted at rest and in transit.
Never Shared
Your credentials are never shared with third parties.
Full Control
Revoke or update credentials at any time.
You add the link in Copilot
Vinkius gives you one connection link. In VS Code's Copilot Chat, you run MCP: Add Server, choose your scope, and paste the link as the server URL.
Token generated successfully
MCP Connection URL
https://edge.vinkius.com/vk_preview_NBvLpXdOI5ehLMBDuWXjBbjUwW8SLFHFZoz8epVV/mcp
Connection Token
vk_live_••••••••
Go to Dashboard

Set it up once. Use FamilySearch API with the AI you already use.

FAQ

Copilot access questions.

01
Which Copilot surface supports this?
The custom MCP server path works in VS Code's Copilot Chat and in the Copilot CLI (copilot mcp add, with the config stored in your mcp-config.json). The consumer Copilot app uses built-in connectors and doesn't accept custom URLs today.
02
If I connect FamilySearch API to Copilot, can I use the same connection in Claude or ChatGPT later?
Yes, and that's the point: the connection is yours, not Copilot's. You paste the same link in any AI you use, and there's nothing new to set up or pay again. Connect a new AI and FamilySearch API is already there.
03
Do I need to hand my FamilySearch API password to Copilot?
Never. You sign in once at Vinkius, and we keep your logins encrypted and away from your AI. Copilot only ever sees the link, and you can remove it whenever you want.
04
What can I actually ask Copilot to do with FamilySearch API?
Whatever the Connector covers: check data, run actions and bring answers back into the session. The Connector page lists every capability your AI gains, with real examples you can copy.
05
Copilot doesn't show the Connector. What do I check?
Open the MCP list in your editor or run copilot mcp list, confirm the server was added with the link pasted exactly as copied, and confirm the Connector is active in your Vinkius account. A deactivated Connector stops responding.
06
Can I remove the access later?
Anytime. Remove the server from your MCP list (or your mcp-config.json) and it's out of your sessions. Your Vinkius account keeps the connection and its history either way, ready for the next AI.
More questions about FamilySearch API? The Connector page answers them. See everything the FamilySearch API Connector can do

About the Connector

What FamilySearch API adds to your AI.

Once you connect it, your AI gains 6 capabilities: the exact actions it can take in FamilySearch API when you ask. The Connector page lists every one of them in detail, alongside the latency we measure in production and prompts worth trying first.

See everything the FamilySearch API Connector can do