Connecting another AI app

Connect any AI app that can use a remote MCP server with a browser sign-in to your FilmScorecard account, and what to do if yours cannot.

Once it is connected, the app can look through what your own screens show you (submissions, judges, scorecards, awards, judge pay and settings) and answer questions about it. It acts as you, so it reaches exactly what you reach and nothing more, and it can change only three things: a film's status, your own flag, and Priority. Everything a connected app can do is in Connecting an AI app.

There are pages of their own for Claude, ChatGPT, Claude Code and Cursor.

Will your app work?

It will if it can add a remote MCP server and sign you in to it through your browser. AI apps call these MCP servers, connectors, custom connectors or integrations, and the browser sign-in OAuth.

It will not if it asks you for an API key, a token or a password. FilmScorecard does not issue any of them: the browser sign-in is the only way in.

For whoever sets it up, the technical detail:

The server speaks MCP over streamable HTTP at the address below. It does not offer the older SSE transport, or a local command to run.
It signs apps in with OAuth 2.1, which the app discovers from the address itself, and the app registers itself. There is no client ID or secret to create or paste.

Before you start

Your organization needs AI access. FilmScorecard switches it on one organization at a time. To check, open Your profile in the menu behind your name and choose the Connections tab: if the Another app row offers How to connect, you have it. If the AI apps card says "AI access isn't on for your organization yet", press Request AI access: it opens our contact form with the request already written. See Connections.
The address. Every app needs the same one. The Another app steps on the Connections tab show it with a Copy button beside it:
```
https://www.filmscorecard.com/api/mcp
```

Connecting it

Find the MCP setting. Look in the app's settings for MCP servers, connectors, custom connectors or integrations.
Add the server. Paste the address. If the app asks what kind of connection it is, choose HTTP, sometimes called streamable HTTP. If it offers fields for a client ID or secret, leave them empty.
Connect. Your browser opens on FilmScorecard.
Sign in, if FilmScorecard asks. If you are not signed in to FilmScorecard in that browser, you get the log-in screen first. Sign in with your emailed code as usual (see Logging in), and you come straight back.
Check the request. The connection page asks whether to let the app in. It shows the app's name, with "wants to connect to your account." under it; Will act as, which is the address you sign in with; and It can, which reads "read and update festival data you already have access to". Make sure it names the app you just added. If you did not just start connecting an app, press Deny, and nothing is connected.
Press Allow. Your browser goes back to the app, which is now connected.

To check it worked, open the Connections tab on your account screen. An app without a row of its own reads Connected, with the date you allowed it, on the Another app row. When more than one is connected there, each line starts with the name the app gave when it connected.

Using it

Ask about your festivals the way you would ask a colleague. For example:

"Which festivals and seasons can you see in FilmScorecard?"
"Give me an overview of this season's submissions and judging."
"List the films in this season that are still In Consideration."

The app starts by finding your festivals, because every other question names an organization, a festival or a season. A status move is always previewed first, and nothing changes until the app asks again to confirm. See Moving films between statuses.

For more to ask, and habits that get better answers, see Using an AI app.

If something goes wrong

What you see	What to do
The app asks for an API key, a token or a header	It cannot connect: FilmScorecard issues none of them.
The app offers only a local command (stdio) or SSE	It cannot connect: the server speaks streamable HTTP only.
The app insists on a client ID and secret	It cannot register itself, so it cannot connect yet. Tell us which app it is.
"AI access isn't enabled for your organization.", with Deny and no Allow	None of your organizations has AI access, or you are signed in on an account that belongs to no organization, such as a judge's. Press Deny so the app stops waiting, then press Request AI access on your Connections tab.
"This connection request has expired or was already answered. Start again from your AI app."	A request does not last long and can be answered once. Connect again from the app.
"This connection request is incomplete. Start again from your AI app."	The page was opened from a bookmark or typed by hand. Connect again from the app.
"That didn't go through. Try again."	Your answer did not reach FilmScorecard. Press Allow again. If it keeps happening, start again from the app.
The app says it was told "Too many calls in the last minute. Wait a moment and try again."	Each person can make 120 calls a minute across every app they have connected. Wait a moment. See 120 calls a minute.

Every other sentence an app can be told is in When the app is refused.

Disconnecting it

Open Your profile in the menu behind your name, and choose the Connections tab.
On the Another app row, press the amber Disconnect beside the app.
Press the amber Disconnect in the dialog.

The app is refused from its next request. Removing it in the app's own settings takes it out of the app, but FilmScorecard keeps listing the connection until you disconnect it on the Connections tab.

Using an AI app: what to ask it, and how to get good answers.
Connecting an AI app: everything a connected app can do, the 34 tools, what it is never given, and every sentence it is told when it is refused.
Your account settings: the Connections tab.