> For the complete documentation index, see [llms.txt](https://docs.theopenpresenter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.theopenpresenter.com/plugins/official-plugins/lyrics-presenter.md).

# Lyrics Presenter

At the moment, we only have integration with myworshiplist.com. This will increase in the future.&#x20;

We also want to add ability for users to save their own songs into the database. Currently, you can add a new song but it won't persist beyond the plugin.

We use a format inspired to OpenSong

Here are some of the basic rules:

1. Separate sections with square brackets(\[ ]) like \[Verse 1].\
   This can be anything from Verse, Chorus, Bridge, and any text you like.
2. Use a single dash(-) to split your section into multiple slides.
3. Add a dot(.) in front of a line to indicate that it is a chord line.\
   Note: At this time, we do not support showing chords yet.

#### Example

```
[Verse]
I know He rescued my soul
His blood has covered my sin
I believe I believe
-
My shame He's taken away
My pain is healed in His name
I believe, I believe
-
I'll raise a banner
'Cause my Lord
Has conquered the grave

[Chorus]
My Redeemer lives
My Redeemer lives
My Redeemer lives
My Redeemer lives

[Bridge]
You lift my burdens
I'll rise with You
I'm dancing on this mountaintop
To see Your kingdom come
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.theopenpresenter.com/plugins/official-plugins/lyrics-presenter.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
