Goals
Reads
- Your goals and your team's, with progress
- Your company's goal categories
Makes changes
- Create goals for yourself or people you manage
- Update details and record progress
- Mark goals complete and add comments
Connect Claude, ChatGPT, Microsoft 365 Copilot and other AI assistants to PerformYard. Ask about goals, meetings, feedback, reviews and reports, and make updates without leaving the conversation. Your PerformYard permissions apply to every request.
Server URLhttps://mcp.talent.performyard.com/mcpCopy URLMCP is turned on company by company. Check these four things before you connect.
Your Customer Success Manager turns on MCP for your company. After that, an administrator can switch it on or off with Enable MCP Server under Administration → AI Assistants → MCP.
You connect with your usual sign-in, including SSO and multi-factor authentication. The assistant never sees your password.
You need a client that can add a remote MCP server with OAuth sign-in, such as Claude, ChatGPT, Claude Code or Microsoft 365 Copilot.
MCP isn't available if your company limits PerformYard to specific IP addresses, because assistants connect from their own networks.
It takes about a minute. There's no API key to set up. Paste the server URL and your assistant sends you to PerformYard to sign in.
In your assistant, add a custom connector or remote MCP server and paste the server URL.
PerformYard opens in your browser. Sign in, review the request, and choose whether to allow changes.
Ask about your goals, meetings, feedback and reviews in your own words.
On Team and Enterprise plans, an organization owner may need to add the connector first.
Depending on your plan, custom connectors may need developer mode or a workspace admin.
Any client that supports remote MCP servers with OAuth can connect. Use the server URL with the Streamable HTTP transport, and leave the client ID, secret and custom headers empty.
Claude Code: run claude mcp add --transport http performyard https://mcp.talent.performyard.com/mcp, then run /mcp and choose Authenticate.
GitHub Copilot in VS Code: add the server URL as an http server in .vscode/mcp.json, then sign in when VS Code prompts you.
The sign-in redirect must go to an https:// or localhost address.
Ask in your own words. The assistant chooses the tools, and it can only see and change what you can in PerformYard. Open an example in Claude or ChatGPT to try it; connect PerformYard there first.
Update my customer retention goal to 92% and note that the new onboarding flow launched.
Give each of my direct reports a goal to finish security training by the end of the quarter.
Reads only look things up. Makes changes updates PerformYard, and only if you allowed changes when you connected.
Meeting tools need your company's Meetings module. Meeting notes and transcripts aren't available.
Private notes stay visible only to their author.
In-progress reviews aren't available, and anonymous reviewers stay anonymous.
Report data can lag recent changes.
The assistant can never do more than you can in PerformYard, and you decide whether it can make changes at all.
Every request is checked against your current PerformYard role. If you can't see a goal, review or report in PerformYard, neither can the assistant.
You choose on the approval screen. Without permission to make changes, the assistant never sees those tools. Reconnect to change your choice.
Private feedback notes stay with their author, anonymous reviewers stay anonymous, and in-progress reviews, meeting notes and transcripts are never returned.
Goals, feedback and review answers the assistant reads are processed by that provider, such as Anthropic or OpenAI, under your company's agreement with them.
You sign in on PerformYard's own page. The assistant gets a token that works only with the MCP server and can't be used to sign in to PerformYard.
Connections last up to 90 days, or 30 days if unused. When an administrator turns off MCP, every connection in the company ends immediately.
Each tool call that runs is recorded with who made it, the assistant, the tool and the outcome. What you asked and what came back are not stored in the log.
Check before you confirm. AI assistants can make mistakes. Review what the assistant plans to change, especially for anything that notifies other people, like giving or requesting feedback.
Most connection problems come down to company settings or an expired sign-in.
That's expected. The server only answers MCP requests from an assistant. Paste the URL into your assistant's connector settings instead.
MCP isn't on for your company, an administrator turned off Enable MCP Server, your account is inactive, or your company uses an IP allow-list. Ask your PerformYard administrator. If MCP was turned off and back on, reconnect, since turning it off ends existing connections.
You connected without allowing changes. Disconnect, reconnect, and allow changes on the approval screen.
The assistant uses your PerformYard permissions. If you can't do the same thing in PerformYard, it can't either. Ask your administrator if your access looks wrong.
Allow pop-ups and redirects for your assistant, then start the connection again from the assistant. Each sign-in link works once and expires after 15 minutes, so an old browser tab won't work.
Connections last up to 90 days, or 30 days if unused, and end when an administrator turns off MCP or your account is deactivated. Reconnect from your assistant to sign in again.
You or your company reached the request limit. Wait a moment and try again. Asking for smaller, more specific results helps.
Still stuck? Email support@performyard.com with your assistant's name, when it happened and any error message.